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

Restore replication after a failure #4

Open
Hespian opened this issue Mar 15, 2021 · 0 comments
Open

Restore replication after a failure #4

Hespian opened this issue Mar 15, 2021 · 0 comments
Labels
enhancement New feature or request

Comments

@Hespian
Copy link
Collaborator

Hespian commented Mar 15, 2021

Right now, when too many ranks have failed, restore might lose some blocks permanently. In this case, an exception is thrown and the user has to obtain the data in some other way (usually by reloading it from disk). This could be improved by restoring the specified replication level after a failure.

The blocks stored on a failed rank should be assigned to new (living) ranks. For better performance, this should be done in a way that only reassigns blocks that were stored on dead ranks and leaves all blocks stored on living ranks untouched. A possible approach could be consistent hashing or similar techniques.

@Hespian Hespian added the enhancement New feature or request label Mar 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant