On Thu, Oct 29, 2009 at 1:18 PM, Edmond Lau <email@example.com> wrote:> I get an UnavailableException.
> I have a freshly started 3-node cluster with a replication factor of
> 2. If I take down two nodes, I can no longer do any writes, even with
> a consistency level of one. I tried on a variety of keys to ensure
> that I'd get at least one where the live node was responsible for one
> of the replicas. I have not yet tried on trunk. On cassandra 0.4.1,
This sounds like the bug we fixed in CASSANDRA-496 on trunk.
If you use QUORUM or ALL consistency, neither write will succeed. If
> Along the same lines, how does Cassandra handle network partitioning
> where 2 writes for the same keys hit 2 different partitions, neither
> of which are able to form a quorum? Dynamo maintained version vectors
> and put the burden on the client to resolve conflicts, but there's no
> similar interface in the thrift api.
you use ONE, both will, and the one with the higher timestamp will
"win" when the partition heals.