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
When a server starts up, if it is already a member of a cluster, it should compare the hostname in its config (or what is read automatically from the OS) against the name it has in the cluster. If this name is different it should update the metastore and cluster with the new hostname/IP.
This means that we'll have to store a local file that has the server ID of this server so that when it starts it can look in the metastore to see which server it is.
This issue is important for people running inside docker containers or people brining up a new server with the backup data from an old machine.
The text was updated successfully, but these errors were encountered:
If the -hostname flag is passed, the node will startup and be accessible from
remote nodes using the specified hostname. At startup, we attempt to update
the hostname if it's different. For data-only nodes, this is pretty straight-forward.
For nodes part of the raft cluster, it is much more complicated as the the cluster
must be up and stable (with a leader) for a the update to take place. The main
complication in this case is that the node starting up will have a different
hostname and will fail to take part of the raft cluster because each other node
does not have this new name in the it's raft peers list. Since this is very problematic
and very easy to break a cluster, this PR just aborts startup and alerts the operator that
some manual actions must be taken to update the raft peer on all raft members before
the hostname can be fully updated.
Fixes#3421
When a server starts up, if it is already a member of a cluster, it should compare the hostname in its config (or what is read automatically from the OS) against the name it has in the cluster. If this name is different it should update the metastore and cluster with the new hostname/IP.
This means that we'll have to store a local file that has the server ID of this server so that when it starts it can look in the metastore to see which server it is.
This issue is important for people running inside docker containers or people brining up a new server with the backup data from an old machine.
The text was updated successfully, but these errors were encountered: