Skip to main navigation Skip to search Skip to main content

Multi-Erasure Locally Recoverable Codes over Small Fields: A Tensor Product Approach

Pengfei Huang, Eitan Yaakobi, Paul H. Siegel

Research output: Contribution to journalArticlepeer-review

Abstract

Erasure codes play an important role in storage systems to prevent data loss. In this work, we study a class of erasure codes called Multi-Erasure Locally Recoverable Codes (ME-LRCs) for storage arrays. Compared to previous related works, we focus on the construction of ME-LRCs over small fields. Our main contribution is a general construction of ME-LRCs based on generalized tensor product codes, and an analysis of their erasure-correcting properties. A decoding algorithm tailored for erasure recovery is given, and correctable erasure patterns are identified. We then prove that our construction yields optimal ME-LRCs with a wide range of code parameters, and present some explicit ME-LRCs over small fields. Next, we show that generalized integrated interleaving (GII) codes can be treated as a subclass of generalized tensor product codes, thus defining the exact relation between these codes. Finally, ME-LRCs are investigated in a probabilistic setting. We prove that ME-LRCs based upon a generalized tensor product construction can achieve the capacity of a compound erasure channel consisting of a family of erasure product channels.

Original languageEnglish
Article number8941037
Pages (from-to)2609-2624
Number of pages16
JournalIEEE Transactions on Information Theory
Volume66
Issue number5
DOIs
StatePublished - May 2020

Keywords

  • Locally recoverable codes
  • capacity-achieving
  • compound channel
  • small fields
  • tensor product codes

All Science Journal Classification (ASJC) codes

  • Information Systems
  • Computer Science Applications
  • Library and Information Sciences

Fingerprint

Dive into the research topics of 'Multi-Erasure Locally Recoverable Codes over Small Fields: A Tensor Product Approach'. Together they form a unique fingerprint.

Cite this