News for hackers. Stuff that matters.
Re:MongoDB 3.4.0-rc3 by mushi on Tuesday February 07, 2017 @12:54PM (#13591127)
I think maybe the doubt is based on case like https://aphyr.com/posts/282-jepsen-postgres which all systems are subject to.
Re:MongoDB 3.4.0-rc3 by continuational on Tuesday February 07, 2017 @04:41PM (#13593096)
That's not a case of inconsistency. There are just three outcomes for a transaction: Committed, Aborted and Unknown.

The client will never experience Committed unless it really is committed, and thus never report that it was successful to the user.

Re:MongoDB 3.4.0-rc3 by throwawayish on Tuesday February 07, 2017 @05:06PM (#13593340)
Uh, no. That article is a bit of a long winded way to say that 2PC with timeouts is 2PC with timeouts.
Re:MongoDB 3.4.0-rc3 by aphyr on Tuesday February 07, 2017 @05:13PM (#13593418)
It might be better to think of it as a limitation of two-generals, rather than 2PC in particular.