hydra-remote-memory · research · also Hydra (FAST 2022)

Hydra remote memory

Hydra is a research resilience layer that erasure-codes individual remote-memory pages and controls fragment placement.

Completion: Each page has k data and r parity fragments on distinct remote machines. Failure-recovery writes wait for all k+r; EC-only completes after k without the same resilience guarantee. Reads can finish with the first k of k+delta requested fragments. [1]

Placement: CodingSets confines choices to disjoint extended groups, then selects less-loaded members. Under the paper's failure model, it trades fewer loss events for larger events, not a reduction in expected data lost. That invariance is not a guarantee for arbitrary rack-correlated failures; see the CodingSets topology control. [1]

Failure scope: Remote unreachability is distinct from silent corruption. The paper defines separate corruption modes and excludes local-network failure without disk fallback. Remote redundancy is not persistent storage. [1]

Artifact mismatch: The README illustrates 8+2, while the pinned header activates NDATAS=4 and NDISKS=NDATAS+2 with IS_PAGE_SIZE=4096. Configuration examples must not be reported as compiled defaults. [2] [3]

Reproduction boundary: The README targets historical Ubuntu, kernel and RDMA stacks. The paper's persistent-memory comparison uses DRAM-based emulation, not measured Optane hardware. No Hydra deployment was run here. [2] [1]

Hesela arithmetic: For a fresh 4+2 page version with only four acknowledged fragments, losing one of those four leaves only three. With all six acknowledged, any two fragment losses leave four. The downloadable model enumerates every loss subset and keeps pending writes unavailable. This is a finite illustrative model, not an observed failure probability. [4] [5]

Relations

related
Carbink, Infiniswap, CodingSets

Citations

  1. Lee et al. Hydra: Resilient and Highly Available Remote Memory. FAST 2022, pp. 181-198; sections 3.3, 4.1, 5 and 7.5. (accessed 2026-11-15)
  2. Hydra authors: README example and historical prerequisites; pinned revision (accessed 2026-11-15)
  3. Hydra authors: active EC configuration and page size; pinned header (accessed 2026-11-15)
  4. Hesela: executable acknowledged-fragment enumeration with explicit assumptions (accessed 2026-11-15)
  5. Hesela: generated 4+2 completion matrix, counts and denominators (accessed 2026-11-15)
Sources & caveats
  • Primary-source synthesis and an original finite counting model, not a native Hydra experiment, benchmark replication or measured reliability estimate.
  • The remote-memory system is unrelated to the Hydra filesystem fuzzer; the slug disambiguates the two projects.

JSON: /data/terms/hydra-remote-memory.json

Published by Hesela team · Updated

Report a correction · Editorial standards · Reuse guidance

Cite this page
Hesela team. Hydra remote memory. Hesela. 2026-11-15. https://hesela.dev/terms/hydra-remote-memory/