ACM Home Page
Please provide us with feedback. Feedback
Digital Library logoTake a look at the new version of this page: [ beta version ]. Tell us what you think.
Nonblocking commit protocols
Full text PdfPdf (1.00 MB)
Source International Conference on Management of Data archive
Proceedings of the 1981 ACM SIGMOD international conference on Management of data table of contents
Ann Arbor, Michigan
SESSION: Transaction management II table of contents
Pages: 133 - 142  
Year of Publication: 1981
ISBN:0-89791-040-0
Author
Dale Skeen  University of California, Berkeley, California
Sponsor
SIGMOD: ACM Special Interest Group on Management of Data
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 9,   Downloads (12 Months): 139,   Citation Count: 83
Additional Information:

abstract   references   cited by   collaborative colleagues  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/582318.582339
What is a DOI?

ABSTRACT

Protocols that allow operational sites to continue transaction processing even though site failures have occurred are called nonblocking. Many applications require nonblocking protocols. This paper investigates the properties of nonblocking protocols. Necessary and sufficient conditions for a protocol to be nonblocking are presented and from these conditions a method for designing them is derived. Both a central site nonblocking protocol and a decentralized nonblocking protocol are presented.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
 
2
{GRAY79} Gray, J. N., "Notes on Database Operating Systems," in Operating Systems: An Advanced Course, Springer-Verlag, 1979.
 
3
{HAMM79} Hammer, M. and Shipman, D., "Reliability Mechanisms for SDD-1: A System for Distributed Databases," Computer Corporation of America, Cambridge, Mass., July 1979.
 
4
{LAMP76} Lampson, B. and Sturgis, H., "Crash Recovery in a Distributed Storage System," Tech. Report, Computer Science Laboratory, Xerox Parc, Palo Alto, California, 1976.
 
5
{LIND79} Lindsay, B.G. et al., "Notes on Distributed Databases", IBM Research Report, no. RJ2571 (July 1979).
6
 
7
{ROTH77} Rothnie, J. B., Jr. and Goodman, N., "A Survey of Research and Development in Distributed Database Management," Proc. Third Int. Conf. on Very Large Databases, IEEE, 1977.
 
8
{SKEE81a} Skeen, D., "A Formal Model of Crash Recovery in a Distributed System", IEEE Transactions on Software Engineering, (to appear).
 
9
{SKEE81b} Skeen, D., "Crash Recovery in a Distributed Database System," Ph. D. Thesis, EECS Dept., University of California, Berkeley (in preparation).
 
10
{STON79} Stonebraker, M., "Concurrency Control and Consistency of Multiple Copies in Distributed INGRES," IEEE Transactions on Software Engineering, May 1979.
 
11
{SCHA78} Schapiro, R. and Millstein, R., "Failure Recovery in a Distributed Database System," Proc. 1978 COMPCON Conference, September 1978.
 
12
{SVOB79} Svobodova, L., "Reliability Issues in Distributed Information Processing Systems," Proc. 9th IEEE Fault Tolerant Computing Conference, Madison, Wisc., June 1979.

CITED BY  83