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
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 maifi.k...@gmail.com wrote:
Hi
How is the locking implemented in cassandra? Say
Hi Maifi,
This is the expected behaviour for updating a value - the newest value
always wins in the event of a conflict (e.g. after two partitions converge).
Your use case is that of incrementing counters, which is not something that
is easily solved in Cassandra at the moment.
There are issues
On Mon, Aug 16, 2010 at 6:07 AM, Maifi Khan maifi.k...@gmail.com wrote:
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.
Not to be too pedantic, but you're misunderstanding how to use
cassandra. When we talk about 'n' we mean
-to-cassandra-replication-and-consistency
b
On Mon, Aug 16, 2010 at 6:07 AM, Maifi Khan maifi.k...@gmail.com wrote:
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
