-
Notifications
You must be signed in to change notification settings - Fork 876
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
变更配置,怎样确保慢的节点,最后也安全退出 #240
Comments
需要业务层自己处理,braft实际上不会主动删数据,垃圾副本的gc由业务层自己进行。 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
设想一个场景, 有三个节点 A B C, 现在 A B 网络比较好,日志都是最新的, C节点的网络比较差。
将conf 变更为 A B D, 这时C因为网络问题一直都没有加入决策。 当变更完毕后,C节点网络才恢复。
A, B, D 三个节点的新主不再会同步信息给C节点。 C节点一直不清楚自己被放弃了。
问题: braft 是怎样处理这样的问题的, 是由braft库解决,还是需要交由业务层解决?
The text was updated successfully, but these errors were encountered: