DIRECT recovery
DIRECT is a research approach that repairs small corrupted regions from distributed replicas while preserving the storage system's update order.
DIRECT combines fine-grained data recovery, local metadata redundancy and recovery ordered with writes. Logical replicas can have different physical file layouts, so a damaged block cannot simply be replaced by the same block from another replica. [1]
Its key-value implementation places a patch request in its own Paxos log entry. The donor supplies the preceding log-prefix state; installation is atomic. Keys absent from that complete range are implicit deletions, including deletions whose tombstones have already been compacted away. Affected historical snapshots need separate handling. [1]
An empty complete range and an incomplete scan are different inputs. Only the former supports removing every local key in that range. The executable example compares range replacement with a merge that preserves a deleted key. [3]
Evaluation used injected errors, not a field trial of extended SSD lifetime. [1] An earlier eight-system study independently showed that replication alone does not guarantee recovery from a single filesystem fault. [2]
Relations
- related
- Read repair, Silent data corruption, State-machine replication, LSM tombstone, Sorted string table
Limitations
- Recovery depends on identifying the affected logical range and obtaining an intact donor at the required consistency point. [1]