A formal approach to replica consistency in directory service

Authors:
Jerzy Brzeziński;Cezary Sobaniec;Dariusz Wawrzyniak
Affiliations:
Poznan University of Technology, Institute of Computing Science, Poznan, Poland;Poznan University of Technology, Institute of Computing Science, Poznan, Poland;Poznan University of Technology, Institute of Computing Science, Poznan, Poland
Venue:
PPAM'09 Proceedings of the 8th international conference on Parallel processing and applied mathematics: Part I
Year:
2009

Citing 8
Cited 0

Efficient and correct execution of parallel programs that share memory

ACM Transactions on Programming Languages and Systems (TOPLAS)
The power of processor consistency

SPAA '93 Proceedings of the fifth annual ACM symposium on Parallel algorithms and architectures
Grapevine: an exercise in distributed computing

Communications of the ACM
Session Guarantees for Weakly Consistent Replicated Data

PDIS '94 Proceedings of the Third International Conference on Parallel and Distributed Information Systems
Sequential Consistency in Distributed Systems

Selected Papers from the International Workshop on Theory and Practice in Distributed Systems
From grapevine to trader: the evolution of distributed directory technology

CASCON '92 Proceedings of the 1992 conference of the Centre for Advanced Studies on Collaborative research - Volume 2
A unified theory of shared memory consistency

Journal of the ACM (JACM)
Optimistic replication

ACM Computing Surveys (CSUR)

Quantified Score

Hi-index	0.00

Visualization

Abstract

Replication is commonly applied in the implementation of directory service as a way to improve availability and efficiency. However, it raises the problem of consistency maintenance, especially important in the case of slow propagation of changes. The delay in propagation may lead to different anomalies in directory service usage. This paper presents an analysis of consistency conditions that are satisfied by the replicated directory entries, and specifies requirements resulting from client's history of execution (session guarantees) that are necessary in order to meet the same conditions in the view on the client side.