Chubby's solution to consistency issue

The chapter about Zookeeper says that the followers in Zookeeper could lag behind the master, so read operations can get stale data, and in contrast, in Chubby, both read and write requests are directed to the master. This has the benefit of increased consistency but the downside of decreased throughput. To mitigate this, Chubby clients cache extensively and the master is responsible for invalidating the caches before completing writes.

Wouldn’t this create a problematic dependency on clients for write operations since Master needs to make sure all clients’ caches are invalidated before it can complete a write?

Course chapter: