Proceedings of the Fifth International Workshop on Data-Intensive Distributed Computing Date 2012
DOI: 10.1145/2286996.2287002
|View full text |Cite
|
Sign up to set email alerts
|

Consistency and fault tolerance for erasure-coded distributed storage systems

Abstract: One challenge in applying erasure codes (or error-correcting codes) to distributed storage systems is to maintain consistency between data and redundancy blocks in the face of crashing servers. We present two access protocols that provide sequential consistency and maximum distance separable fault tolerance at the same time. The protocols use sequence numbers to recover a consistent version in the presence of failures or partial writes. The first (pessimistic) PSW protocol uses a master per stripe to execute u… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

1
16
0

Year Published

2013
2013
2022
2022

Publication Types

Select...
5
1
1

Relationship

0
7

Authors

Journals

citations
Cited by 11 publications
(17 citation statements)
references
References 25 publications
1
16
0
Order By: Relevance
“…The parities outside the quorum too need to be updated, but this is let to happen in the background. It can be carried out efficiently using a standard technique using differentials [ 7 , 8 , 9 , 10 ], which is outside the scope of this work.…”
Section: Grid Quorumsmentioning
confidence: 99%
See 2 more Smart Citations
“…The parities outside the quorum too need to be updated, but this is let to happen in the background. It can be carried out efficiently using a standard technique using differentials [ 7 , 8 , 9 , 10 ], which is outside the scope of this work.…”
Section: Grid Quorumsmentioning
confidence: 99%
“…Apart from quorum systems, another popular mechanism for consistency is the class of primary-based protocols, where each data block x has an associated primary, which is responsible for coordinating operations on x . For example, Reference [ 9 ] proposed an update model assuming a primary which serializes the update executions, and, similarly, in Reference [ 10 ], the node storing a data block enforces serialized writes, while updates are disseminated in a best effort manner to the redundant blocks, and stale reads are possible, i.e., there is no consistency guarantee.…”
Section: Introductionmentioning
confidence: 99%
See 1 more Smart Citation
“…If D 1,1 is a frequently updated data block (i.e., block D 1,1 is modified by D 1,1 ), then all parity blocks of the same stripe should be updated. Parity blocks are updated by a commutative operation in an RS-coded system [23]; therefore, the updates at parity nodes S 3 and S 4 can be done in any order. …”
Section: Handling Frequently Updated Datamentioning
confidence: 99%
“…Most existing studies on I/O scheduling in erasure-coded storage systems (i.e., RAID storage systems, and erasurecoded storage clusters) are focused on the issues of reconstruction optimization [ [23], and so forth. Unfortunately, little attention has been paid to the topic of 'node recoveries concurrent with user writes'.…”
Section: Related Workmentioning
confidence: 99%