Hi Traian,
There is your problem. You are using RF=1, meaning that each node is
responsible for its range, and nothing more. So when a node goes down, do
the math, you just can't read 1/5 of your data.
This is very cool for performances since each node owns its own part of the
data and any write
I will let commiters or anyone that has knowledge on Cassandra internal
answer this.
From what I understand, you should be able to insert data on any up node
with your configuration...
Alain
2013/2/14 Traian Fratean traian.frat...@gmail.com
You're right as regarding data availability on that
Generally data isn't written to whatever node the client connects to. In
your case, a row is written to one of the nodes based on the hash of the
row key. If that one replica node is down, it won't matter which
coordinator node you attempt a write with CL.ONE: the write will fail.
If you want
hinted hand
off won't help since the write doesn't satisfy CL.ONE.
From: Bryan Talbot btal...@aeriagames.com
To: user@cassandra.apache.org
Sent: Thursday, February 14, 2013 8:30 AM
Subject: Re: Cluster not accepting insert while one node is down
Generally data
We probably need more info like the RF of your cluster and CL of your reads
and writes. Maybe could you also tell us if you use vnodes or not.
I heard that Astyanax was not running very smoothly on 1.2.0, but a bit
better on 1.2.1. Yet, Netflix didn't release a version of Astyanax for
C*1.2.
