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 …
Doesn't "Wait for all log shards" imply a third sync cross-DC hop? For any log segment without a local Paxos leader, won't a given DC need to wait for propose, ack, AND commit to be able to append its txns to the global txn log, which is a prereq to apply any later txn? cc @evan
-
-
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).
- Još 9 drugih odgovora
Novi razgovor -
-
-
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.