You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 19, 2017. It is now read-only.
When servers start up, the first thing they always do is send a JoinRequest to any node that can handle it. But the logic for joining the cluster is independent of server states. So, when a server starts and is elected leader, it will often attempt to join through another node which will proxy the join back to the leader. This is obviously just an odd behavior. The join logic should recognize the local server as the leader and complete the join with no configuration change.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When servers start up, the first thing they always do is send a
JoinRequest
to any node that can handle it. But the logic for joining the cluster is independent of server states. So, when a server starts and is elected leader, it will often attempt to join through another node which will proxy the join back to the leader. This is obviously just an odd behavior. The join logic should recognize the local server as the leader and complete the join with no configuration change.The text was updated successfully, but these errors were encountered: