-
Notifications
You must be signed in to change notification settings - Fork 880
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
Snapshot建立之后,如何做log compaction? #6
Comments
|
@chenzhangyi 谢谢解答! 另外想问一下,counter的example里面on_snapshot_load是在raft node刚启动的时候调用一次,之后就不会调用了吗?为什么要限制leader不执行这个逻辑? 有一个场景是,把服务从一个IDC搬迁到另一个IDC,直接copy所有的snapshot和log到新IDC起一套raft group,leader是需要从snapshot load数据的吧? 是否只有leader会创建snapshot? |
|
@chenzhangyi 谢谢! |
Closed
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
关于counter的example的实现中,snapshot创建之后,是braft自动去做了log compaction吗?
如果是的话,如何保证的snapshot的时间戳和log里面的一致的?因为on_apply里面可能会有CPU heavy的操作导致application status和log差好几分钟的数据。
另外,是否只有leader创建snapshot就可以了?
The text was updated successfully, but these errors were encountered: