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
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: