Talk:Two-phase commit protocol: Difference between revisions

Revision as of 02:47, 5 September 2009

Revision as of 17:18, 8 September 2009

Line 39:

Two phase commit is actually resilient to however many failures. Once the coordinator decides what to do and writes it to the log file, no matter how many failures occur, at some point the transaction will finalize. The wiki article is incorrect - the referenced paper does not say that 2PC FAILS, it says that in some cases everything must block for potentially a long time (which they argue is not acceptable in most applications). But (the basic, blocking) 2PC IS resilient to multiple failures. The problem is that it is blocking, and yes, if you remove the blocking part, it is no longer resilient (duh). Hope this helps, I think the article should be corrected but the author might want to make the corrections himself. Radu

== Wikipedia text on Dynamic 2PC (D2PC) copied "as is" to a COIT 2008 conference paper ==

The text was copied to the following paper:

: ''An Efficient Fault Tolerance Protocols for Mobile Computing Systems''

: * Kumar Surender **,Kumar Parveen *** Chauhan R.K

: * Lecturer Deptt. Of I.T., H.C.T.M. Kaithal

: ** Professor Deptt. Of CSE, APIIT, Panipat.

: ***Chairman Deptt. Comp. Sc. & Application KUK

(see paper [http://www.rimtengg.com/coit2008/proceedings/NW28.pdf here])

that appeared in [http://www.rimtengg.com/coit2008/coit08.html COIT 2008].

More [[Wikipedia]] text is embedded there with reference to neither Wikipedia nor the original D2PC paper:

[http://www.springerlink.com/content/pv12p828kk616258/ Yoav Raz, ''The Dynamic Two Phase Commitment (D2PC) protocol'', ICDT 1995]

This is a strange practice for a scientific paper, that should be discouraged.

-- [[User:Comps|Comps]] ([[User talk:Comps|talk]]) 17:18, 8 September 2009 (UTC)