Aha. We have 0.6.2
So 0.6.3 is the right version to use?
thanks
Maifi
On Wed, Nov 3, 2010 at 4:34 PM, Jonathan Ellis wrote:
> You are looking at obsolete code.
>
> CHANGES.txt
> 0.6.3
> * don't reject reads at CL.ALL (CASSANDRA-1152)
>
>
> On Wed, Nov 3, 2010
Hi
Inside org.apache.cassandra.thrift, in CassandraServer.java, it seems
that read operation for Consistency level "all" is not supported.
Is this the case?
Does this mean there is no way to read from all the copy? if there
are 3 copies of data, I would like to read all of them.
I gave the cod
:
> The quorum write would fail, but the data would not be rolled back. Assuming
> the offline nodes recover, the data would eventually replicate.
>
> This question belongs on the user list, though.
>
> -Original Message-----
> From: Maifi Khan
> Date: Thu, 19 Aug 2010 13
Hi
I have a question in the following scenario.
Say we have 10 nodes, Replication factor is 5.
Now, say, for Row X, Column Y, data is replicated to node 1,2,3,4,5
and current value is 10
Say, I issue a write command with value “20” to Row X, column Y with
quorum(n/2+1=3 nodes). Say it updated 1 an
; is where the local write happens (if a coordinator is reponsible for
> the mutation key). RowMutationVerbHandler does the same work on the
> remote nodes and acknowledges the writes.
>
> Gary.
>
> On Mon, Aug 16, 2010 at 08:07, Maifi Khan wrote:
>> Hi
>> How is the lo
Hi
How is the locking implemented in cassandra? Say, I have 10 nodes and
I want to write to 6 nodes which is (n+1)/2.
Will it lock 6 nodes first and then start writing? Or will it write
one by one and see if it can write to 6 nodes.
How is this implemented? What package does this locking?
Thanks in
