control-connection: reconnect after discounted down signal#849
Closed
dkropachev wants to merge 1 commit intomasterfrom
Closed
control-connection: reconnect after discounted down signal#849dkropachev wants to merge 1 commit intomasterfrom
dkropachev wants to merge 1 commit intomasterfrom
Conversation
Collaborator
Author
|
Closed in favor of #854 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #847
Summary
Cluster.on_down()report whether down handling actually ransignal_connection_failure()return that actual handling resultRisk
Low. These methods are internal; callers now get a stricter signal that separates conviction-policy decisions from cluster state transitions.
Testing
workflow-testpassed; overall managed run timed out duringworkflow-build-2(fb89a55a3c13fe9e1fc961bf3fde577201e57b280ec634084a2108f8da41a101).