Skip to content
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

Closed
pauldix opened this issue Jan 31, 2015 · 2 comments
Closed

Should be able to replace a failed server #1472

pauldix opened this issue Jan 31, 2015 · 2 comments

Comments

@pauldix
Copy link
Member

pauldix commented Jan 31, 2015

There should be a query command to replace a downed server with one that has recently joined the cluster.

replace "downedhost.foo.com" with "newhost.foo.com"

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.

@pauldix pauldix added this to the 0.9.0 milestone Mar 14, 2015
@toddboom toddboom modified the milestones: 0.9.0, 1.0.0 May 8, 2015
@beckettsean beckettsean modified the milestones: 0.9.6, 1.0.0 Sep 17, 2015
@corylanou corylanou self-assigned this Sep 24, 2015
@corylanou
Copy link
Contributor

This should be done after #1471

@corylanou corylanou removed their assignment Nov 17, 2015
@jwilder jwilder removed this from the 0.10.0 milestone Feb 1, 2016
@jsternberg
Copy link
Contributor

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
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants