Xuzhe Liu, Yuchong Hu, Dan Feng, Leihua Qin, Hai Zhou, Xin Zhao, Renzhi Xiao
{"title":"Repair friendly wide-stripe erasure coding for in-memory key–value stores","authors":"Xuzhe Liu, Yuchong Hu, Dan Feng, Leihua Qin, Hai Zhou, Xin Zhao, Renzhi Xiao","doi":"10.1016/j.sysarc.2025.103516","DOIUrl":null,"url":null,"abstract":"<div><div>Erasure coding is a low-cost redundancy mechanism over replication for in-memory key–value stores by storing stripes of data and parity chunks. <em>Wide stripes</em> are recently proposed to suppress the fraction of parity chunks in a stripe for extreme storage savings. However, wide stripes aggravate the repair penalty, and existing repair-efficient approaches for erasure coding fail to address this effectively.</div><div>We investigate two representative approaches, locally repairable codes (LRCs) and regenerating codes (RGCs), which reduce repair overhead in distributed storage. Building on this foundation, we propose two systematic solutions to address the repair penalty in wide-stripe erasure coding: (i) <em>Combine Locality (CL)</em>, a cross-rack data placement mechanism for Azure-LRC combining parity and topological locality, (ii) <em>Repair-Contribution-Based Placement (RCBP)</em>, a cross-rack data placement mechanism for Hitchhiker codes (a subclass of RGCs), strategically co-locating chunks with high repair contributions in the same rack. We apply CL-based LRC and RCBP-based Hitchhiker codes to in-memory key–value (KV) stores, augmenting them with efficient encoding and update schemes. Experiments on Amazon EC2 show that CL reduces the single-chunk repair time by up to 90.5% compared to locality-based state-of-the-art. RCBP improves repair throughput by up to 19.3% and 44.6% compared to original Hitchhiker and RS codes, respectively.</div></div>","PeriodicalId":50027,"journal":{"name":"Journal of Systems Architecture","volume":"167 ","pages":"Article 103516"},"PeriodicalIF":3.7000,"publicationDate":"2025-07-14","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"0","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"Journal of Systems Architecture","FirstCategoryId":"94","ListUrlMain":"https://www.sciencedirect.com/science/article/pii/S1383762125001882","RegionNum":2,"RegionCategory":"计算机科学","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"Q1","JCRName":"COMPUTER SCIENCE, HARDWARE & ARCHITECTURE","Score":null,"Total":0}
引用次数: 0
Abstract
Erasure coding is a low-cost redundancy mechanism over replication for in-memory key–value stores by storing stripes of data and parity chunks. Wide stripes are recently proposed to suppress the fraction of parity chunks in a stripe for extreme storage savings. However, wide stripes aggravate the repair penalty, and existing repair-efficient approaches for erasure coding fail to address this effectively.
We investigate two representative approaches, locally repairable codes (LRCs) and regenerating codes (RGCs), which reduce repair overhead in distributed storage. Building on this foundation, we propose two systematic solutions to address the repair penalty in wide-stripe erasure coding: (i) Combine Locality (CL), a cross-rack data placement mechanism for Azure-LRC combining parity and topological locality, (ii) Repair-Contribution-Based Placement (RCBP), a cross-rack data placement mechanism for Hitchhiker codes (a subclass of RGCs), strategically co-locating chunks with high repair contributions in the same rack. We apply CL-based LRC and RCBP-based Hitchhiker codes to in-memory key–value (KV) stores, augmenting them with efficient encoding and update schemes. Experiments on Amazon EC2 show that CL reduces the single-chunk repair time by up to 90.5% compared to locality-based state-of-the-art. RCBP improves repair throughput by up to 19.3% and 44.6% compared to original Hitchhiker and RS codes, respectively.
期刊介绍:
The Journal of Systems Architecture: Embedded Software Design (JSA) is a journal covering all design and architectural aspects related to embedded systems and software. It ranges from the microarchitecture level via the system software level up to the application-specific architecture level. Aspects such as real-time systems, operating systems, FPGA programming, programming languages, communications (limited to analysis and the software stack), mobile systems, parallel and distributed architectures as well as additional subjects in the computer and system architecture area will fall within the scope of this journal. Technology will not be a main focus, but its use and relevance to particular designs will be. Case studies are welcome but must contribute more than just a design for a particular piece of software.
Design automation of such systems including methodologies, techniques and tools for their design as well as novel designs of software components fall within the scope of this journal. Novel applications that use embedded systems are also central in this journal. While hardware is not a part of this journal hardware/software co-design methods that consider interplay between software and hardware components with and emphasis on software are also relevant here.