Online reconfiguration in replicated databases based on group communication

Kemme, Bettina; Bartoli, Alberto; Babaoğlu, Özalp

doi:10.1109/dsn.2001.941398

Cited by 57 publications

(119 citation statements)

References 9 publications

Supporting

Mentioning

119

Contrasting

Order By: Relevance

“…On the sequel we describe the recovery protocols proposed in [22], focusing on the data transfer and synchronization points.…”

Section: Datamentioning

confidence: 99%

“…Multiple recovery protocols for replicated databases are presented in [22]. All of them are proposed for database replication protocols sharing the following characteristics: update everywhere protocol -ROWAA approach [16]-, based on total order broadcast -without a terminating phase-propagating a message per transaction -constant interaction [28]-and virtual synchrony.…”

Section: Protocols By Kemme Bartoli and Babaoǧlumentioning

confidence: 99%

“…In this paper, we briefly describe some database recovery protocols proposed in the literature [21,19,22,8,3,20,5,7] and surveyed in [14] emphasizing how they face the amnesia phenomenon. This study also gives special importance to the database replication protocols they are designed for, because as it was depicted in [14], the recovery protocols are very dependent from the characteristics of the replication protocols used, and the information that these replication protocols store.…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Reviewing Amnesia Support in Database Recovery Protocols

Juan-Marín

Garcia-Munoz

Armendáriz-Iñigo

et al. 2007

On the Move to Meaningful Internet Systems 2007: CoopIS, DOA, ODBASE, GADA, and IS

View full text Add to dashboard Cite

Replication is used for providing highly available and fault-tolerant information systems, which are constructed on top of replication and recovery protocols. An important aspect when designing these systems is the assumed failure model. Replicated databases literature last trends consist in adopting the crash-recovery with partial amnesia failure model because in most cases it shortens the recovery times. But, despite the large use of such failure model we consider that most of these works do not handle accurately the amnesia phenomenon. Therefore, in this paper we survey some works, analyzing their amnesia support. In this study, we focus on primary component membership systems. The same principles could be applied for partitionable or mobile systems, but we have not surveyed them.

show abstract

“…On the sequel we describe the recovery protocols proposed in [22], focusing on the data transfer and synchronization points.…”

Section: Datamentioning

confidence: 99%

Section: Protocols By Kemme Bartoli and Babaoǧlumentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Reviewing Amnesia Support in Database Recovery Protocols

Juan-Marín

Garcia-Munoz

Armendáriz-Iñigo

et al. 2007

On the Move to Meaningful Internet Systems 2007: CoopIS, DOA, ODBASE, GADA, and IS

View full text Add to dashboard Cite

show abstract

“…A more general discussion about how to efficiently integrate group communication primitives and database recovery is beyond the scope of this paper. For further reference see, e.g., [6,26,29].…”

Section: Database Recoverymentioning

confidence: 99%

Pronto: High availability for standard off-the-shelf databases

Pedone

Frølund²

2008

Journal of Parallel and Distributed Computing

View full text Add to dashboard Cite

Enterprise applications typically store their state in databases. If a database fails, the application is unavailable while the database recovers. Database recovery is time consuming because it involves replaying the persistent transaction log. To isolate end-users from database failures we introduce Pronto, a protocol to orchestrate the transaction processing by multiple, standard databases so that they collectively implement the illusion of a single, highly-available database. Pronto is a novel replication protocol that handles nondeterminism without relying on perfect failure detection, does not require any modifications in existing applications and databases, and allows databases from different providers to be part of the replicated compound.

show abstract

“…Note that most recoverable applications (e.g., replicated databases [15]) demand uniform [11] delivery for broadcast messages. This means that a message is not delivered until the group communication system can ensure that it has been received by all message target processes 2 .…”

Section: Fault Tolerancementioning

confidence: 99%

Parallel Interconnection of Broadcast Systems with Multiple FIFO Channels

Marín

Cholvi

Jiménez

et al. 2009

On the Move to Meaningful Internet Systems: OTM 2009

View full text Add to dashboard Cite

Abstract. This paper proposes new protocols for the interconnection of FIFO-and causal-ordered broadcast systems, thus increasing their scalability. They use several interconnection links between systems, which avoids bottleneck problems due to the network traffic, since messages are not forced to go throughout a single link but instead through the several links we establish. General architectures to interconnect FIFOand causal-ordered systems are proposed. Failure management is also discussed and a performance analysis is given, detailing the benefits introduced by these interconnection approaches that are able to easily increase the resulting interconnection bandwidth.

show abstract

Online reconfiguration in replicated databases based on group communication

Cited by 57 publications

References 9 publications

Reviewing Amnesia Support in Database Recovery Protocols

Reviewing Amnesia Support in Database Recovery Protocols

Pronto: High availability for standard off-the-shelf databases

Parallel Interconnection of Broadcast Systems with Multiple FIFO Channels

Contact Info

Product

Resources

About