-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
[bug:master] change of leader each time to the one who last started/restarted #2804
Comments
locally not reproduced:
|
but if enable -resumeState=true
|
after restarted master2_1 becomes promoted
|
i add debug
https://github.com/chrislusf/seaweedfs/blob/master/weed/server/raft_server.go#L120
Remove deleted peers |
Fixing the work of snapshots led to #2833 |
@chrislusf The presence of snapshots on several master servers at startup causes conflicts when choosing a leader. It worked while the raft was created without logs and snapshots. |
this is also related to #2847 ? |
@chrislusf I did not see the point in repairing the current raft. Since I plan to store the full topology also in the raft. |
with raftBootstrap=false max volume restored from raft logs
|
sw moved to hashicorp raft #2868 add param |
change of leader each time to the one who last started/restarted
version
weed master run cmd:
logs:
The text was updated successfully, but these errors were encountered: