-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
Should be able to replace a failed server #1472
Comments
This should be done after #1471 |
We no longer support clustering in the open source version so I'm going to close this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There should be a query command to replace a downed server with one that has recently joined the cluster.
That command should copy any shards that existed on "downedhost.foo.com" from other servers in the cluster to "newhost.foo.com"
Once all the shards have been copied over, newhost should be marked as up and ready to answer queries. downedhost should be forcibly removed from the cluster.
Obviously, this will only work if their replication factor is > 1 and the other servers have copies of those shards. The brokers will also have to log the data for each shard as it is copied from that time so that it can pick up any writes that happened while it was copying the shard.
The text was updated successfully, but these errors were encountered: