Not sure why it's different for the nodes at the end of the ring. But I'm going
to assume Quorum is working as expected and it's an artifact of the way the
ring ownership is calculated.
Cheers
-
Aaron Morton
Freelance Cassandra Developer
@aaronmorton
http://www.thelastpickle.co
Hi,
Thanks for explaining: As I understood each node now only displays
it's local view of the the data it cotains, and not the global view
anymore.
One more question:
Why do the nodes at the end of the ring only show the % load from 2
nodes and not from 3?
We are always writing with quorum, so th
I'm not sure what the fix is.
When using an order preserving partitioner it's up to you to ensure the ring is
correctly balanced.
Say you have the following setup…
node : token
1 : a
2 : h
3 : p
If keys are always 1 character we can say each node own's roughly 33% of the
ring. Because we kn
Hi,
I will wait until this is fixed beforeI upgrade, just to be sure.
Shall I open a new ticket for this issue?
Thanks,
Thibaut
On Sun, Aug 21, 2011 at 11:57 AM, aaron morton wrote:
> This looks like an artifact of the way ownership is calculated for the OOP.
> See https://github.com/apache/ca
This looks like an artifact of the way ownership is calculated for the OOP. See
https://github.com/apache/cassandra/blob/cassandra-0.8.4/src/java/org/apache/cassandra/dht/OrderPreservingPartitioner.java#L177
it was changed in this ticket
https://issues.apache.org/jira/browse/CASSANDRA-2800
The c
Hi,
we were using apache-cassandra-2011-06-28_08-04-46.jar so far in
production and wanted to upgrade to 0.8.4.
Our cluster was well balanced and we only saved keys with a lower case
md5 prefix. (Orderpreserving partitioner).
Each node owned 20% of the tokens, which was also displayed on each
nod
