never mind , I see that if leader/owner dies, the other replicas can simply
use whoever has the highest count of the leader bucket,
though not the authoritative number
On Tue, May 31, 2011 at 1:21 AM, Yang wrote:
> thanks Sylvain, I agree with what you said for the first few paragraphs
> J
thanks Sylvain, I agree with what you said for the first few paragraphs
Jeremy corrected me just now.
regarding the last point, you are right in using the term "by operation",
but you should also note that it's a leader
"data ownership", in the meaning that the leader has the authoritative po
>I went through https://issues.apache.org/jira/browse/CASSANDRA-1072
>and realize that the consistency guarantees of Counters are a bit different
>from those of regular columns,
Not anymore.
> so could you please confirm that the following are true?
>1) comment
>https://issues.apache.org/jira/b
thanks, got it
I looked at the code more closely, the response handler between the
coordinator and itself as leader, and between leader and replicas, are
shared,
so the coordinator can indeed wait for the count replication to finish for
ALL
yang
On Mon, May 30, 2011 at 6:51 PM, Jeremy Hanna wrot
Some more recent documentation can be found here:
http://wiki.apache.org/cassandra/Counters but even that may be out of date.
One thing that has been added is multiple consistency levels are supported.
There are a lot of other tickets that have been completed post 1072. Search
for "cassandra
I went through https://issues.apache.org/jira/browse/CASSANDRA-1072
and realize that the consistency guarantees of Counters are a bit different
from those of regular columns, so could you please confirm
that the following are true?
1) comment
https://issues.apache.org/jira/browse/CASSANDRA-1072?f
