crdb-release-23.1: Move from StatePause->StateReplicate on heartbeat response when possible #1
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.
Backports etcd-io#52 on behalf of @tbg.
Move from StatePause->StateReplicate on heartbeat response when possible
See individual commits. Essentially, when a fully caught-up follower was
reported unreachable, it'd transition to
StateProbebut then wouldn'trecover from that via heartbeats (once they resumed).
This caused some issues in CRDB because we rely on the reported status
to reason about the safety of leadership changes, etc.
This PR makes it such that StateProbe resolves on its own: when the
leader hears back from the follower via a heartbeat, it sends an
empty MsgApp, and as response to this moves the follower back into
StateProbe.
Touches cockroachdb/cockroach#104304.
Touches cockroachdb/cockroach#101624.
Signed-off-by: Tobias Grieger [email protected]