Distributed Storage Codes with Repair-by-Transfer and Non-achievability of Interior Points on the Storage-Bandwidth Tradeoff

TL;DR

This paper introduces a simple exact-repair code for distributed storage at minimal repair bandwidth, and proves that certain interior points on the storage-bandwidth tradeoff are unachievable under exact-repair, revealing a new tradeoff boundary.

Contribution

It presents a repair-by-transfer code for the minimum bandwidth point and demonstrates the non-achievability of interior points under exact-repair, establishing a new fundamental limit.

Findings

Exact-repair code for minimum bandwidth point with simple graphical description.

Interior points on the storage-bandwidth tradeoff are not achievable under exact-repair.

Identification of helper node pooling as a key constraint in exact-repair scenarios.

Abstract

Regenerating codes are a class of recently developed codes for distributed storage that, like Reed-Solomon codes, permit data recovery from any subset of k nodes within the n-node network. However, regenerating codes possess in addition, the ability to repair a failed node by connecting to an arbitrary subset of d nodes. It has been shown that for the case of functional-repair, there is a tradeoff between the amount of data stored per node and the bandwidth required to repair a failed node. A special case of functional-repair is exact-repair where the replacement node is required to store data identical to that in the failed node. Exact-repair is of interest as it greatly simplifies system implementation. The first result of the paper is an explicit, exact-repair code for the point on the storage-bandwidth tradeoff corresponding to the minimum possible repair bandwidth, for the case when d=n-1. This code has a particularly simple graphical description and most interestingly, has the ability to carry out exact-repair through mere transfer of data and without any need to perform arithmetic operations. Hence the term `repair-by-transfer'. The second result of this paper shows that the interior points on the storage-bandwidth tradeoff cannot be achieved under exact-repair, thus pointing to the existence of a separate tradeoff under exact-repair. Specifically, we identify a set of scenarios, termed `helper node pooling', and show that it is the necessity to satisfy such scenarios that over-constrains the system.