Re: CL.ONE gives UnavailableException on ok node

2011-04-15 Thread Jonathan Ellis
Yes, if you want to keep writes available w/ RF=1 then you need to use CL.ANY. On Fri, Apr 15, 2011 at 3:48 PM, Mick Semb Wever wrote: > On Fri, 2011-04-15 at 15:43 -0500, Jonathan Ellis wrote: >> Sure sounds like you have RF=1 to me. > > Yes that's right. > > I see... so the answer here is that

Re: CL.ONE gives UnavailableException on ok node

2011-04-15 Thread Mick Semb Wever
On Fri, 2011-04-15 at 15:43 -0500, Jonathan Ellis wrote: > Sure sounds like you have RF=1 to me. Yes that's right. I see... so the answer here is that i should be using CL.ANY ? (so the write goes through and hinted handoff can get it to the correct node latter on). ~mck -- "The fox condemns t

Re: CL.ONE gives UnavailableException on ok node

2011-04-15 Thread Jonathan Ellis
Sure sounds like you have RF=1 to me. On Fri, Apr 15, 2011 at 7:45 AM, Mick Semb Wever wrote: > Just experienced something i don't understand yet. > > Running a 3 node cluster successfully for a few days now, then one of > the nodes went down (server required reboot). > After this the other two n

CL.ONE gives UnavailableException on ok node

2011-04-15 Thread Mick Semb Wever
Just experienced something i don't understand yet. Running a 3 node cluster successfully for a few days now, then one of the nodes went down (server required reboot). After this the other two nodes kept throwing UnavailableExceptions like UnavailableException() at org.apache.cassandra.se