Skip to content



Paxos Chubby

  • The network might drop messages between replicas
  • I kinda feel like “multi-“ part can be elegantly decomposed from the whole system
  • Also, it seems like I have been doing the distinguished proposer in the wrong way
  • " Paxos must force future coordinators to select that same value in order to ensure continued agreement” — How to force, I don’t quite understand
  • The reason why this works is subtle (and I don’t really understand)
  • We use a catch-up mechanism to enable lagging replicas to catch up with leading replicas
  • It is also to do “chaining” of multiple message in Paxos, which we don’t prepare to implement
  • How to test: failure injection
  • Our client-server also miss a proper seq number (client can implement this trivially)


Google Spanner: Google's Globally-Distributed Database

Google Chubby

Industry News: Search Engine Land

Google File System

Google Bigtable

Google MapReduce