home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.databases
- Path: sparky!uunet!usc!rpi!usenet.coe.montana.edu!news.u.washington.edu!uw-beaver!ubc-cs!alberta!ozsu
- From: ozsu@cs.UAlberta.CA (Tamer Ozsu)
- Subject: Re: distributed transactions
- Message-ID: <ozsu.714454469@simonette>
- Sender: news@cs.UAlberta.CA (News Administrator)
- Nntp-Posting-Host: simonette.cs.ualberta.ca
- Organization: University of Alberta, Edmonton, Canada
- References: <1736k9INNjhh@agate.berkeley.edu> <BtCrA6.Iuy@cup.hp.com> <173oogINNmrp@agate.berkeley.edu>
- Date: Sat, 22 Aug 1992 03:34:29 GMT
- Lines: 44
-
- mao@triplerock.CS.Berkeley.EDU (Mike Olson) writes:
-
- >In <BtCrA6.Iuy@cup.hp.com>, dhepner@cup.hp.com (Dan Hepner) asks for
- >details on how non-blocking commit protocols handle network partitions:
-
- >> Maybe you can explain how this apparent dilemma is addressed:
- >>
- >> Time 1: node n acknowledges prepare
- >> Time 2: node n notes an inability to communicate with anyone else, in
- >> particular any site capable of being the transaction coordinator
- >> Time 3: still no communications, patience exhausted at node n
-
- >here's what the distributed systems theorists say: a partition splits
- >a network into two pieces. whichever piece contains a majority of
- >the nodes in the original network may continue processing. nodes in
- >the minority clique cannot make further updates until the partition is
- >repaired.
-
- >there are some obvious problems with this -- for example, if no clique
- >contains a majority of the nodes in the original network, no one can
- >make progress.
-
- Actually, this won't be a problem. Protocols dealing with network
- partitioning use a weighted voting strategy where the nodes are
- assigned votes such that one of the partitions will always have more
- votes than the other. The problem is with multiple partitioning. Dale
- Skeen, in the various articles that were mentioned in other messages
- talks about this. The whole thing is also treated in our book
- "Principles of Distributed Database Systems", Prentice-Hall, 1991.
-
-
- >the added complexity of three-phase commit, coupled with the fact that
- >a clever adversary can force blockage anyway, have meant that it hasn't
- >gotten a lot of attention by commercial vendors. in real life, what
- >people do is spend a lot of money on redundant, highly reliable
- >communications systems. when something crashes, some expensive employees
- >get it working again fast.
-
- I agree. There are not too many vendors which implement 2PC either.
- --
- ____________________________________________________________________________
- M. Tamer Ozsu Internet: ozsu@cs.ualberta.ca
- Department of Computing Science Tel: (403) 492-2860; Fax: (403) 492-1071
- University of Alberta Edmonton, Alberta, Canada T6G 2H1
-