raft: remove MsgApp flow control management dependence on heartbeats #130532
+723
−277
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.
This commit does the following:
Instead of unpausing the follower and maybe sending a MsgApp when receiving a heartbeat response, it does the same thing but on heartbeat timeout if the follower is supporting the leader. Otherwise, it sends MsgFortifyLeader to the follower who is not supporting the leader.
This change is guarded by SupportFromEnabled(). If it flips to true, it will stop depending on heartbeat responses. If it flips to false, it will start depending on heartbeat responses again.
NOTE: future PRs will stop heartbeats all together if storeliveness is enabled.
Fixes: #130493
Epic: None
Release note: None