Grokking the System Design Interview, Volume II
Vote

0% completed

​

Summary: Chubby

Summary

  1. Chubby is a distributed lock service used inside Google systems.
  2. It provides coarse-grained locking (for hours or days) and is not recommended for fine-grained locking (for seconds) scenarios. Due to this nature, it is more suited for high-read and rare write scenarios.
  3. Chubby's primary use cases include naming service, leader election, small files storage, and distributed locks.
  4. A Chubby Cell basically refers to a Chubby cluster. A chubby cell has more than one server (typically 3-5 at least) known as replicas. 5

.....

.....

.....

Like the course? Get enrolled and start learning!
S

Shan

· 4 years ago

In the high level architecture it says:

The master writes directly to its own local database, which gets synced asynchronously to all the replicas

Yes on this summary page it says:

To ensure strong consistency, Chubby master sends all write requests to the replicas. After receiving acknowledgments from the majority of replicas in the cell, the master sends an acknowledgment to the client who initiated the write.

So in regards to replication, is Chubby sync or async?