2008
DOI: 10.1109/tc.2007.70830
|View full text |Cite
|
Sign up to set email alerts
|

STAR : An Efficient Coding Scheme for Correcting Triple Storage Node Failures

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

1
156
0
1

Year Published

2009
2009
2019
2019

Publication Types

Select...
4
3
1

Relationship

0
8

Authors

Journals

citations
Cited by 224 publications
(158 citation statements)
references
References 33 publications
1
156
0
1
Order By: Relevance
“…All failures occurred in the data array portion is most difficult to recover, so assuming all failures occur in the data array portion. The core idea of this method is to find valid decoding chains to recover the loss elements on failure nodes, which is similar to the Zig-Zag decoding method [8] but a more concise valid decoding chains searching algorithm.…”
Section: Basic Encoding and Decoding Methodsmentioning
confidence: 99%
See 2 more Smart Citations
“…All failures occurred in the data array portion is most difficult to recover, so assuming all failures occur in the data array portion. The core idea of this method is to find valid decoding chains to recover the loss elements on failure nodes, which is similar to the Zig-Zag decoding method [8] but a more concise valid decoding chains searching algorithm.…”
Section: Basic Encoding and Decoding Methodsmentioning
confidence: 99%
“…In the case of m is 8, Figure 5 shows the amount of XOR operations required to store a 100M file when f is from 2 to 50. It is not difficult to see from this figure, the required binary XOR operations to store a 100M file is less than 8 10 13 even when the fault tolerant ability is as high as 50, and all of these operations can be completed by a most common computing node soon. …”
Section: Operational Workloadmentioning
confidence: 99%
See 1 more Smart Citation
“…Other parity-based redundancy schemes included STAR, HoVer, GRID, and Bˆ, the latter of which typified the tendency of such approaches to focus on the data layout pattern, independent of the number of underlying devices [13,14,18,29]. Typically, these data layouts were subsequently declustered data across homogenous, uniform, devices, and the majority could be classified as variations of low-density parity-codes similar to those used for erasure coding in the communications domain, such as the Luby LT codes, and their Tornado and Raptor variants [16,17,28].…”
Section: Previous Workmentioning
confidence: 99%
“…Because of this storage efficiency, MDS codes are highly favorable, and a lot of research has been done to construct them. Examples of MDS codes are the well known Reed Solomon codes, EVENODD [1], [2], B-code [24], X-code [25], RDP [7], and STAR-code [9]. It is evident that in the case of r erasures, one needs to communicate all the surviving information during the repair process.…”
Section: Introductionmentioning
confidence: 99%