-
Notifications
You must be signed in to change notification settings - Fork 694
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow Module blocking operations (not blocked on keys) to succeed when cluster is down #693
Conversation
Signed-off-by: KarthikSubbarao <[email protected]>
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## unstable #693 +/- ##
============================================
- Coverage 70.20% 70.08% -0.13%
============================================
Files 111 110 -1
Lines 60242 60102 -140
============================================
- Hits 42295 42122 -173
- Misses 17947 17980 +33
|
Signed-off-by: KarthikSubbarao <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Just a minor comment about the test case.
Signed-off-by: KarthikSubbarao <[email protected]>
Signed-off-by: KarthikSubbarao <[email protected]>
…down errors Signed-off-by: KarthikSubbarao <[email protected]>
Signed-off-by: KarthikSubbarao <[email protected]>
Signed-off-by: KarthikSubbarao <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome. Thank you!
Thank you - I updated the PR title and description because we made this fix generic to Module blocking operations (which are not blocked on keys) |
…o#693) Module Authentication using a blocking implementation currently gets rejected when the "cluster is down" from the client timeout cron job (`clientsCronHandleTimeout`). This PR exempts clients blocked on Module Authentication from being rejected here. --------- Signed-off-by: KarthikSubbarao <[email protected]>
…o#693) Module Authentication using a blocking implementation currently gets rejected when the "cluster is down" from the client timeout cron job (`clientsCronHandleTimeout`). This PR exempts clients blocked on Module Authentication from being rejected here. --------- Signed-off-by: KarthikSubbarao <[email protected]>
…o#693) Module Authentication using a blocking implementation currently gets rejected when the "cluster is down" from the client timeout cron job (`clientsCronHandleTimeout`). This PR exempts clients blocked on Module Authentication from being rejected here. --------- Signed-off-by: KarthikSubbarao <[email protected]> Signed-off-by: Ping Xie <[email protected]>
Module Authentication using a blocking implementation currently gets rejected when the "cluster is down" from the client timeout cron job (`clientsCronHandleTimeout`). This PR exempts clients blocked on Module Authentication from being rejected here. --------- Signed-off-by: KarthikSubbarao <[email protected]> Signed-off-by: Ping Xie <[email protected]>
Proposing a fix for this issue - #619 - and adding tests.
Module blocking operations (which are not blocked on keys) currently gets rejected when the "cluster is down" from the client timeout cron job (
clientsCronHandleTimeout
). Example: Module Authentication with a blocking implementation.This PR exempts clients blocked by a Module (but not on keys) from being rejected here on a failed cluster state.