The Couchbase 2.0 manual describes network partitioning as a potential issue.
But I didn’t see how (if) Couchbase 2.0 deal with such issues on the datastore side.
My question is how is CAS implemented in a cluster and how does CAS operations deal with the split-brain problem? Is there a cluster wide lock? Is it last writer wins?
The same question was asked to our Google Groups list: http://groups.google.com/group/couchbase/browse_thread/thread/e0d543d9b17f9c77
It’s down at the bottom of the thread, posts starting on Aug 30
Perry