8000 Restore replication after a failure · Issue #4 · ReStoreCpp/ReStore · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
Restore replication after a failure #4
Open
@Hespian

Description

@Hespian

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0