2014
DOI: 10.1007/978-3-319-14472-6_3
|View full text |Cite
|
Sign up to set email alerts
|

Be General and Don’t Give Up Consistency in Geo-Replicated Transactional Systems

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
13
0

Year Published

2016
2016
2022
2022

Publication Types

Select...
3
3

Relationship

2
4

Authors

Journals

citations
Cited by 18 publications
(13 citation statements)
references
References 17 publications
0
13
0
Order By: Relevance
“…In Alvin [24], Turcu et al outline a commitment protocol comprising a concurrency control layer on top of partial order broadcast, using rotating leaders over a sequence of delivery slots, not dissimilar to Mencius [7]. Each slot has an exclusive leader; its failure requires an election before a value may be proposed in that slot, revealing Alvin's adversarial nature.…”
Section: A Parallels Outside Of Consensusmentioning
confidence: 99%
See 1 more Smart Citation
“…In Alvin [24], Turcu et al outline a commitment protocol comprising a concurrency control layer on top of partial order broadcast, using rotating leaders over a sequence of delivery slots, not dissimilar to Mencius [7]. Each slot has an exclusive leader; its failure requires an election before a value may be proposed in that slot, revealing Alvin's adversarial nature.…”
Section: A Parallels Outside Of Consensusmentioning
confidence: 99%
“…Atomic commitment protocols have perceptibly evolved in the same vein as their consensus and atomic broadcast counterparts, relying on process exclusivity and multiple distinct phases to attain a commit/abort agreement over a set of resource managers, and in some cases [24], on the deterministic ordering of transactions in a log.…”
Section: A Parallels Outside Of Consensusmentioning
confidence: 99%
“…In addition, its graph-based dependency linearization mechanism that is adopted to define the final order of execution of commands may easily suffer from complex dependency patterns. Instead, Alvin [11] avoids the expensive computation on the dependency graphs enforced by EPaxos via a slot-centric decision, but it still suffers from the same vulnerability to conflicts of EPaxos: a command's leader is not able to decide on a fast path if it observes discordant opinions from a quorum of nodes. That is not the case of CAESAR, whose fast decision scheme is optimized to increase the probability of deciding in two communication delays regardless of discordant feedbacks.…”
Section: Related Workmentioning
confidence: 99%
“…To overcome this limitation, protocols aimed at allowing multiple nodes to operate as command leaders at the same time [9], [10], [11] have been proposed. Such solutions provide implementations of Generalized Consensus [12], a variant of Consensus that agrees on a common order of non-commutative (or conflicting) commands.…”
Section: Introductionmentioning
confidence: 99%
“…To solve the fairness problem, a node must be allowed to choose which other nodes to communicate with based on the performance of its network links, as in the EPaxos [6] and Alvin [7] algorithms, both of which do not employ a unique leader, and allow any node to choose the closest (in terms of latency) set of nodes to reach agreement. EPaxos and Alvin are based on a novel but intricate algorithmic idea first introduced in EPaxos, which is difficult to generalize to devise other algorithms with different performance characteristics.…”
Section: Introductionmentioning
confidence: 99%