Conversation
A follower forwards a coordinator write to whichever coordinator it last saw leading, and the leader serves it only while it is ready. Nothing holds it ready between the follower reading that it leads and the forwarded write arriving, so the write can be declined for a state that has already passed, and no state the caller can read beforehand settles whether the next one will be served. The refusal is how the caller learns. Every query in this file asks for something the test has just arranged, which rules out the reasons a leader declines for good and leaves only the ones that pass, so they share one seam that asks again on a budget. Asking a follower to remove the leader is the exception, being declined for good, and is asked once. The leader's own reason does not cross the wire, so the text a caller matches on cannot tell a leader that was not ready from one that refused for good, and only the caller's own request separates them.
Ignition
added this pull request to stack #4925
September 24, 2026 09:37
Ignition
marked this pull request as ready for review
September 24, 2026 09:37
|
as51340
requested changes
Sep 24, 2026
as51340
left a comment
Contributor
There was a problem hiding this comment.
same as here #4920 (review)
Ignition
removed this pull request from stack #4925
September 24, 2026 10:36
Ignition
marked this pull request as draft
September 24, 2026 13:47
Ignition
added this pull request to stack #4930
September 24, 2026 14:27
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.



A follower forwards a coordinator write to whichever coordinator it last saw leading, and the leader serves it only while it is ready. Nothing holds it ready between the follower reading that it leads and the forwarded write arriving, so the write can be declined for a state that has already passed, and no state the caller can read beforehand settles whether the next one will be served. The refusal is how the caller learns.
Every query in this file asks for something the test has just arranged, which rules out the reasons a leader declines for good and leaves only the ones that pass, so they share one seam that asks again on a budget. Asking a follower to remove the leader is the exception, being declined for good, and is asked once. The leader's own reason does not cross the wire, so the text a caller matches on cannot tell a leader that was not ready from one that refused for good, and only the caller's own request separates them.