On Wednesday, August 14, I'll be giving a livestreamed talk with @fauna, discussing various approaches for transactional isolation in globally distributed systems, including Spanner, @CockroachDB, FaunaDB, @YugaByteDB, @VoltDB, Percolator, and TiDB.http://www2.fauna.com/wcdistributedarchitectures …
I may have forgotten to explain this in the talk, but you can (in most cases) pick a log segment with a local leader, because, in general, every DC will have leaders for one (or more) log segments. If all local leaders are down, yes, you'd have to proxy, which would add hops.
-
-
That all makes sense and was covered well! The question is whether you have to wait to hear what was committed by remote log segments (3 WAN hops, see https://twitter.com/natevanben/status/1196457975407370240 …) before applying txns that were committed by a local log segment (2 WAN hops).
-
Oh, I think I get what you're driving at here. Yes, I think you need to get a commit index, and specifically, one for the decision to seal the log window, but I don't think that's in the blocking path of txns--if you couple windows to the Raft term, leader can seal independently
- 8 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.