Re: quorum calculation seems to depend on previous selected nodes

2011-01-18 Thread Stephen Connolly
On 18 January 2011 07:15, Samuel Benz wrote: > On 01/17/2011 09:28 PM, Jonathan Ellis wrote: >> On Mon, Jan 17, 2011 at 2:10 PM, Samuel Benz wrote: > Case1: > If 'TEST' was previous stored on Node1, Node2, Node3 -> The update will > succeed. > > Case2: > If 'TEST' was prev

Re: quorum calculation seems to depend on previous selected nodes

2011-01-17 Thread Samuel Benz
On 01/17/2011 09:28 PM, Jonathan Ellis wrote: > On Mon, Jan 17, 2011 at 2:10 PM, Samuel Benz wrote: Case1: If 'TEST' was previous stored on Node1, Node2, Node3 -> The update will succeed. Case2: If 'TEST' was previous stored on Node2, Node3, Node4 -> The update will >

Re: quorum calculation seems to depend on previous selected nodes

2011-01-17 Thread Jonathan Ellis
On Mon, Jan 17, 2011 at 2:10 PM, Samuel Benz wrote: >>> Case1: >>> If 'TEST' was previous stored on Node1, Node2, Node3 -> The update will >>> succeed. >>> >>> Case2: >>> If 'TEST' was previous stored on Node2, Node3, Node4 -> The update will >>> not work. >> >> If you have RF=2 then it will be st

Re: quorum calculation seems to depend on previous selected nodes

2011-01-17 Thread Samuel Benz
On 01/17/2011 05:08 PM, Jonathan Ellis wrote: > On Mon, Jan 17, 2011 at 9:55 AM, Samuel Benz wrote: >> We have a cluster with 4 nodes. ReplicationFactor is 2, ReplicaPlacment >> is the RackAwareStrategy and the EndpointSnitch is the >> PropertyFileEndpointSnitch (with two data center and two racks

Re: quorum calculation seems to depend on previous selected nodes

2011-01-17 Thread Peter Schuller
> Adding CL.TWO would be easy enough. :) True, but the obvious generalization is to be able to select an arbitrary replica count and that seemed like a bigger change to the API. But if CL.TWO would be considered clean enough... I may submit a jira/patch. -- / Peter Schuller

Re: quorum calculation seems to depend on previous selected nodes

2011-01-17 Thread Jonathan Ellis
Adding CL.TWO would be easy enough. :) On Mon, Jan 17, 2011 at 12:12 PM, Peter Schuller wrote: >> I think you should just tell everybody that if you want to use QUORUM you >> need RF >= 3 for it to be meaningful. >> >> No one would use QUORUM with RF < 3 except in error. > > Well, strictly speaki

Re: quorum calculation seems to depend on previous selected nodes

2011-01-17 Thread Peter Schuller
> I think you should just tell everybody that if you want to use QUORUM you > need RF >= 3 for it to be meaningful. > > No one would use QUORUM with RF < 3 except in error. Well, strictly speaking you could have an application designed to talk to Cassandra at QUORUM and an operator may choose to d

Re: quorum calculation seems to depend on previous selected nodes

2011-01-17 Thread David Boxenhorn
I think you should just tell everybody that if you want to use QUORUM you need RF >= 3 for it to be meaningful. No one would use QUORUM with RF < 3 except in error. On Mon, Jan 17, 2011 at 6:08 PM, Jonathan Ellis wrote: > On Mon, Jan 17, 2011 at 9:55 AM, Samuel Benz > wrote: > > We have a clus

Re: quorum calculation seems to depend on previous selected nodes

2011-01-17 Thread Jonathan Ellis
On Mon, Jan 17, 2011 at 9:55 AM, Samuel Benz wrote: > We have a cluster with 4 nodes. ReplicationFactor is 2, ReplicaPlacment > is the RackAwareStrategy and the EndpointSnitch is the > PropertyFileEndpointSnitch (with two data center and two racks each). > > My understanding is, that with this par

quorum calculation seems to depend on previous selected nodes

2011-01-17 Thread Samuel Benz
Dear List I found a strange behavior on our mini cluster during update with consistency level quorum. We have a cluster with 4 nodes. ReplicationFactor is 2, ReplicaPlacment is the RackAwareStrategy and the EndpointSnitch is the PropertyFileEndpointSnitch (with two data center and two racks each)