PACEMAKER: Avoiding HeART attacks in storage clusters with disk-adaptive redundancy

TL;DR

PACEMAKER is a novel system that enables disk-adaptive redundancy in storage clusters by proactively managing data layouts and transitions, significantly reducing transition overhead while maintaining space efficiency and data protection.

Contribution

It introduces PACEMAKER, a low-overhead orchestrator that mitigates transition overload in disk-adaptive redundancy schemes through proactive data organization and transition timing.

Findings

Transition IO overhead is reduced to under 5% of cluster bandwidth.

PACEMAKER achieves 14-20% space savings in large production clusters.

It maintains data protection without transition overload.

Abstract

Data redundancy provides resilience in large-scale storage clusters, but imposes significant cost overhead. Substantial space-savings can be realized by tuning redundancy schemes to observed disk failure rates. However, prior design proposals for such tuning are unusable in real-world clusters, because the IO load of transitions between schemes overwhelms the storage infrastructure (termed transition overload). This paper analyzes traces for millions of disks from production systems at Google, NetApp, and Backblaze to expose and understand transition overload as a roadblock to disk-adaptive redundancy: transition IO under existing approaches can consume 100% cluster IO continuously for several weeks. Building on the insights drawn, we present PACEMAKER, a low-overhead disk-adaptive redundancy orchestrator. PACEMAKER mitigates transition overload by (1) proactively organizing data layouts to make future transitions efficient, and (2) initiating transitions proactively in a manner that avoids urgency while not compromising on space-savings. Evaluation of PACEMAKER with traces from four large (110K-450K disks) production clusters show that the transition IO requirement decreases to never needing more than 5% cluster IO bandwidth (0.2-0.4% on average). PACEMAKER achieves this while providing overall space-savings of 14-20% and never leaving data under-protected. We also describe and experiment with an integration of PACEMAKER into HDFS.