-
Notifications
You must be signed in to change notification settings - Fork 9.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proposal: Introduce Follower Replication in Raft #11357
Comments
@Fullstop000 maybe it is better for us to paste the benchmark result here. |
Another benefit I think is to reduce the pressure of the leader when the leader has more followers or learners. |
This is an OK idea. Just need to justify the complexity from some benchmark results, ideally from practical experience/use cases. |
@xiang90 is it ok to add some extra fields in
Not all of new fields will be used in different message types. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 21 days if no further activity occurs. Thank you for your contributions. |
Summary
In the origin raft protocol, a follower can only receive new raft logs and snapshots from the leader, which could be insufficient in some situations. For example, when a raft cluster is distributed in different data centers, log replication can is expensive due to the frequent cross-DC network transmission. In this case, internal follower-to-follower transfer in one data center can be far more efficient than the traditionally stipulated leader-to-follower transfer.
Relate docs
tikv/rfcs#33
The text was updated successfully, but these errors were encountered: