Is ZooKeeper always consistent in terms of CAP theorem?

Question

Is that correct that ZooKeeper is always CP (in terms of CAP theorem)? Or is there anyway to use it as AP for service discovery needs?

Answer 1

Zookeeper is not A, and can't drop P. So it's called CP apparently. In terms of CAP theorem, "C" actually means linearizability.

linearizability : if operation B started after operation A successfully completed, then operation B must see the the system in the same state as it was on completion of operation A, or a newer state.

But, Zookeeper has Sequential Consistency - Updates from a client will be applied in the order that they were sent.

ZooKeeper does not in fact simultaneously consistent across client views. http://zookeeper.apache.org/doc/trunk/zookeeperProgrammers.html#ch_zkGuarantees

ZooKeeper does not guarantee that at every instance in time, two different clients will have identical views of ZooKeeper data. Due to factors like network delays, one client may perform an update before another client gets notified of the change. Consider the scenario of two clients, A and B. If client A sets the value of a znode /a from 0 to 1, then tells client B to read /a, client B may read the old value of 0, depending on which server it is connected to. If it is important that Client A and Client B read the same value, Client B should should call the sync() method from the ZooKeeper API method before it performs its read.

ZooKeeper provides "sequential consistency". This is weaker than linearizability but is still very strong, much stronger than "eventual consistency". ZooKeeper also provides a sync command. If you invoke a sync command and then a read, the read is guaranteed to see at least the last write that completed before the sync started.

linearizability, writes should appear to be instantaneous. Imprecisely, once a write completes, all later reads (where “later” is defined by wall-clock start time) should return the value of that write or the value of a later write. Once a read returns a particular value, all later reads should return that value or the value of a later write."

In Zookeeper they have sync() method to use where we need something like linearizability.

Serializability is a guarantee about transactions, or groups of one or more operations over one or more objects. It guarantees that the execution of a set of transactions (usually containing read and write operations) over multiple items is equivalent to some serial execution (total ordering) of the transactions.

Refer :

• http://zookeeper-user.578899.n2.nabble.com/Consistency-in-zookeeper-td7578531.html
• http://www.bailis.org/blog/linearizability-versus-serializability/
• Difference between Linearizability and Serializability

Answer 2

No, you cannot change consistency guarantees in current versions of ZooKeeper like you can in some other systems.

You can add a local cache to your clients which will make them have read only data if the cluster goes down, but in terms of CAP that is still not A because it needs to be available for updates as well as reads.

If ZK offers too strong levels of consistency for your service discovery needs, you should try researching other options, e.g. Eureka, Consul or etcd.

Possibly related reads:

• https://tech.knewton.com/blog/2014/12/eureka-shouldnt-use-zookeeper-service-discovery/
• https://github.com/Netflix/eureka/wiki/FAQ
• https://www.consul.io/intro/vs/zookeeper.html