Re:Waltz: A Distributed Write-Ahead Log
by millrawr on Monday September 09, 2019 @04:13PM
(#20921945)
Persisting executed transactions to a log with their read/write sets, and then determining if they actually commit also starts to sound like http://web.eecs.umich.edu/~michjc/eecs584/Papers/cidr11_hyde... to me
[ Parent
| on HN ]
Re:Waltz: A Distributed Write-Ahead Log
by ryanworl on Monday September 09, 2019 @04:22PM
(#20922038)
Yes, it is more similar to Hyder than FoundationDB if you persist the R/W sets to the log itself. FoundationDB gets around this by only keeping the lock table in memory. When any process in the transaction pipeline fails, the master (which holds the version number) advances the version far enough into the future that any in-progress transaction would fail because it is too old.