cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yuki Morishita (JIRA)" <>
Subject [jira] [Created] (CASSANDRA-5076) Murmur3Partitioner#describeOwnership calculates ownership% wrong
Date Tue, 18 Dec 2012 20:38:13 GMT
Yuki Morishita created CASSANDRA-5076:

             Summary: Murmur3Partitioner#describeOwnership calculates ownership% wrong
                 Key: CASSANDRA-5076
             Project: Cassandra
          Issue Type: Bug
    Affects Versions: 1.2.0 rc1
            Reporter: Yuki Morishita
            Priority: Minor

When I issued 'nodetool status' on Murmur3-partitioned cluster I got the following output:

$ bin/nodetool -p 7100 status                                                            
Datacenter: datacenter1
|/ State=Normal/Leaving/Joining/Moving
--  Address           Load       Owns   Host ID                               Token      
UN         24.78 KB   66.7%  ace7e54c-9fe1-4b23-83b0-949772b24c30  -9223372036854775808
UN         29.22 KB   66.7%  67146442-dbfd-449c-82e1-26729b8ac89c  -3074457345618258603
UN         6.19 KB    66.7%  3fab9f18-daf3-4452-8b9c-204ea0ee2e15  3074457345618258602

Notice that 'Owns' percentages add up to 200%.

I think the problem is that Murmur3Partitioner#describeOwnership currently calculate ownership%
based on [0, Long.MAX_VALUE] range, but we have to consider about negative tokens.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message