Repository navigation
[CRE-7136] Fail remote executable requests early on unreachable quorum after an error - #24169
Merged
Merged
Conversation
Contributor
|
✅ No conflicts with other open PRs targeting |
…m after an error Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
bolekk
force-pushed
the
cre-7136-quorum-unreachable-on-error
branch
from
November 9, 2026 23:34
eb1edeb to
463fa0e
Compare
bolekk
marked this pull request as ready for review
November 9, 2026 23:34
pavel-raykov
approved these changes
Nov 10, 2026
cedric-cordenier
approved these changes
Nov 10, 2026
russell-stern
approved these changes
Nov 10, 2026
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
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.
CRE-7136
The remote executable client checks whether quorum is still reachable only on OK responses.
OnErrornever does, so a mix of OK and error responses can leave every quorum unreachable while the request keeps waiting. Example with N=4, F=1: OK(A), OK(B), err(x), err(y). The request then hangs until expiry, which can take up to ~2×timeout+10s because the expiry ticker period equals the timeout.OnErrorfails with the existingConsensusFailed"response quorum unreachable" error once neither an OK quorum nor any error quorum can still be reached.Client-side only, no wire change, so a staged rollout is safe.
Deployment Validation
Existing canaries;
response quorum unreachable, failing earlywarnings may appear where requests previously timed out.🤖 Generated with Claude Code