Re:It’s Time to Move on from Two Phase Commit
by lurker458 on Friday January 25, 2019 @03:29PM
(#19002187)
True, but it's O(n^2) complexity instead of O(n) complexity (1000 shards would lead to 1M reads instead of 4k)
If they're not persisted at the receiving side, how does it handle a crash before committing on the receiving node ? Keeping previous versions indefinitely on sending nodes to permit requesting the old values doesn't work, so this introduces a time bound on how long a crashed node has to recover (granted, this could still mean weeks)
Re:It’s Time to Move on from Two Phase Commit
by abadid on Friday January 25, 2019 @05:01PM
(#19002949)
This requires a longer response that I have time write now. Please check back tomorrow night ...
Re:It’s Time to Move on from Two Phase Commit
by abadid on Saturday January 26, 2019 @09:16PM
(#19010005)
magicalhippo asked a similar question both with regard to complexity and garbage collection. I think it is best to combine these threads, so please see my response there ... https://news.ycombinator.com/item?id=19003212
Re:It’s Time to Move on from Two Phase Commit
by oggy on Friday January 25, 2019 @03:49PM
(#19002363)
I don't understand your point about only a subset of shards running code that may abort. Since we are talking about transactions, if there is even a single shard S that may abort (based on its state), then all other shards must also abort when S aborts. Which would imply that all other shards must also read the state of S before they commit. Am I missing something?
But remember, 2PC requires 4 messages per worker (so 40 messages total in your example).