Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

Stefan Pappe

dblp:58/6510 · DBLP profile ↗
← Back
2ranked-venue papers
0as first author
0since 2021 · last 1993
—ORCID · none

Domains — the database's venue-derived domains; a paper can count in several

Systems, architecture and hardware · 1Databases, data management, data science and information retrieval · 1

Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.

Computer architecture, parallel and distributed computing, and storage systems
1 paper
Distributed systems · 100%

Topics — the 4 heaviest of 5, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Distributed systems › distributed database
commit protocol
0.011993
Open Commit Protocols Tolerating Commission Failures · ACM Trans. Database Syst. 1993
Distributed systems › distributed database
distributed transactions
0.011993
Open Commit Protocols Tolerating Commission Failures · ACM Trans. Database Syst. 1993
Distributed systems
fault tolerance
0.011993
Open Commit Protocols Tolerating Commission Failures · ACM Trans. Database Syst. 1993
Distributed systems › distributed system architecture
open distributed systems
0.011993
Open Commit Protocols Tolerating Commission Failures · ACM Trans. Database Syst. 1993

Methods — techniques the papers use, named apart from their topics

two-phase commit · 0.0message complexity analysis · 0.0
YearPublicationVenuePosition
1993 Open Commit Protocols Tolerating Commission Failures
abstract
To ensure atomicity of transactions in distributed systems so-called 2-phase commit (2PC) protocols have been proposed. The basic assumption of these protocols is that the processing nodes involved in transactions are “sane,” i.e., they only fail with omission failures, and nodes eventually recover from failures. Unfortunately, this assumption is not realistic for so-called Open Distributed Systems (ODSs), in which nodes may have totally different reliability characteristics. In ODSs, nodes can be classified into trusted nodes (e.g., a banking server) and nontrusted nodes (e.g., a home PC requesting a remote banking service). While trusted nodes are assumed to be sane, nontrusted nodes may fail permanently and even cause commission failures to occur. In this paper, we propose a family of 2PC protocols that tolerate any number of omission failures at trusted nodes and any number of commission and omission failures at nontrusted nodes. The proposed protocols ensure that (at least) the trusted nodes participating in a transaction eventually terminate the transaction in a consistent manner. Unlike Byzantine commit protocols, our protocols do not incorporate mechanisms for achieving Byzantine agreement, which has advantages in terms of complexity: Our protocols have the same or only a slightly higher message complexity than traditional 2PC protocols.
Kurt Rothermel, Stefan Pappe
ACM Trans. Database Syst.2
1990 Open Commit Protocols for the Tree of Processes Model
abstract
The authors propose three different two-phase commit (2PC) protocols that ensure that, even in the presence of permanent node failures, all sane nodes participating in a particular transaction eventually terminate the transaction in a consistent way. A node is defined to be sane if it eventually recovers from failures. These protocols, called open 2PC protocols, are based on a tree-of-processes model and provide means for transferring the coordinator function within process trees. Besides describing the open 2PC protocols in detail, the authors compare these protocols with regard to their message and time complexity. They also include a discussion of related work.>
Kurt Rothermel, Stefan Pappe
ICDCS2