> That makes sense with my symptoms... I was doing a CL=ONE for write and a
> CL=ALL for read, expecting that to be sufficient.
>
> I will try both set to ALL and see if I get better consistency.
Just keep in mind that with ALL queries will fail with just a single
node down. (This is why QUORUM
If you do CL=ONE write + CL=ALL read, then it seems OK...
You should better to stay in this thread until some of experts would
answer your question.
2011/5/14 Ryan Hadley :
> Thanks Maki,
>
> That makes sense with my symptoms... I was doing a CL=ONE for write and a
> CL=ALL for read, expecting t
Thanks Maki,
That makes sense with my symptoms... I was doing a CL=ONE for write and a
CL=ALL for read, expecting that to be sufficient.
I will try both set to ALL and see if I get better consistency.
-Ryan
On May 14, 2011, at 4:41 AM, Maki Watanabe wrote:
> It depends on what you really u
It depends on what you really use which CL for your operations.
Your RF is 2, so if you read/write with CL=ALL, your r/w will be
always consistent. If your read is CL=ONE, you have chance to read old
data anytime, decommission is not matter. CL=QUORUM on RF=2 is
semantically identical with CL=ALL.
Hi,
I'm running Cassandra (0.7.4) on a 4 node ring. It was a 3 node ring, but we
ended up expanding it to 4... So then I followed the many suggestions to
rebalance the ring. I found a script that suggested I use:
# ~/nodes_calc.py
How many nodes are in your cluster? 4
node 0: 0
node 1: 42535
