Re: RE: UnavailableException with 3 nodes and RF=2

2010-09-14 Thread Aaron Morton
[mailto:martin.grabmuel...@eleven.de] Sent: 14 September 2010 09:54To: user@cassandra.apache.orgSubject: RE: UnavailableException with 3 nodes and RF=2 When you write with QUORUM, RF/2+1 of the nodes cassandra *wants to write*to have to be up.  In your case, RF/2+1 = 2, that means, the two nodes responsiblefor

RE: UnavailableException with 3 nodes and RF=2

2010-09-14 Thread Chris Jansen
. Thanks again. Chris From: Dr. Martin Grabmüller [mailto:martin.grabmuel...@eleven.de] Sent: 14 September 2010 09:54 To: user@cassandra.apache.org Subject: RE: UnavailableException with 3 nodes and RF=2 When you write with QUORUM, RF/2+1 of the nodes cassandra *wants to write* to have to be

Re: UnavailableException with 3 nodes and RF=2

2010-09-14 Thread Sylvain Lebresne
On Tue, Sep 14, 2010 at 10:43 AM, Chris Jansen wrote: > Hi All, > > > > I’m a newbie to Cassandra so I could have a configuration issue here, I am > using the latest stable release 0.6.0. > > > > I have created a cluster of 3 nodes, a keyspace with RF=2 and a rack unaware > replication strategy. W

RE: UnavailableException with 3 nodes and RF=2

2010-09-14 Thread Dr . Martin Grabmüller
When you write with QUORUM, RF/2+1 of the nodes cassandra *wants to write* to have to be up. In your case, RF/2+1 = 2, that means, the two nodes responsible for the write have to be up, not any two nodes. Each write which tries to the node with token 78502309573904554351249603414557542595 and