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

how to deal with data move #191

Open
hedap2p opened this issue Jan 23, 2018 · 1 comment
Open

how to deal with data move #191

hedap2p opened this issue Jan 23, 2018 · 1 comment

Comments

@hedap2p
Copy link

hedap2p commented Jan 23, 2018

I check the code,find rebanlance only switch master with least_loaded_slave,no data is moved or deleted.
If disk will full,we need move some data to a new server,how to deal with this situation?

@newpoo
Copy link
Contributor

newpoo commented Jan 24, 2018

Good question!

Internally we have a command "expand" to expand a cluster. It uses existing APIs in rocksdb_admin.thrift to operate the hosts involved. At a high level, to move a shard from host A to B, we do the followings.

  1. backup the shard from A to HDFS.
  2. restore the shard from HDFS to B.
  3. remove the shard from host A.

We didn't include the command in the public repo because it requires some refactoring to remove the internal dependencies. Also, we are now working on an automatic cluster management system, which will take precedence over the current script based solution. We will make new cluster management system in the public repo once it's in production at Pinterest.

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

2 participants