[
https://issues.apache.org/jira/browse/CASSANDRA-1553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12930452#action_12930452
]
Jon Hermes commented on CASSANDRA-1553:
---------------------------------------
{noformat}
$ bin/nodetool -h localhost ring
Address Status State Load Owns Token
155711579810515450140957394391963122371
127.0.0.2 Up Normal 7.57 KB 41.54%
56247759826792015654375534268862190753
127.0.0.3 Up Normal 7.57 KB 09.70%
72749652544211640932560301980848705886
127.0.0.1 Up Normal 7.57 KB 48.76%
155711579810515450140957394391963122371
$ bin/nodetool -h localhost ring
Address Status State Load Owns Token
164941942527574387143433761941151641333
127.0.0.1 Up Normal 10.27 KB 19.68%
28276783988490678116658263059846526307
127.0.0.3 Up Normal 10.27 KB 73.39%
153144415326481392832217809981610293616
127.0.0.2 Up Normal 10.27 KB 06.93%
164941942527574387143433761941151641333
$ bin/nodetool -h localhost ring
Address Status State Load Owns Token
74848299015461299193324859323238443723
127.0.0.2 Up Normal 10.27 KB 83.77%
47232172623663922874593218770379172593
127.0.0.1 Up Normal 10.27 KB 14.59%
72053652013445961630779772805427567567
127.0.0.3 Up Normal 10.27 KB 01.64%
74848299015461299193324859323238443723
{noformat}
Cutting the "issue a warning if..." by jbellis request.
Current progress: writing test cases for RP and OPP describeOwnership() methods
now. Gotta show off the shinies first, of course.
> warn of imbalanced ranges in nodetool ring
> ------------------------------------------
>
> Key: CASSANDRA-1553
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1553
> Project: Cassandra
> Issue Type: Improvement
> Components: Tools
> Reporter: Jonathan Ellis
> Assignee: Jon Hermes
> Priority: Minor
> Fix For: 0.6.7, 0.7.1
>
> Attachments: ringer
>
>
> I'd like to enhance nodetool ring to show the % of the token range that it is
> responsible for according to the partitioner (that is, before considering
> replication). For RandomParitioner this is easy. For OPP we can estimate
> using describe_splits. I'd also like to issue a warning if any node N has
> more than 25% more of the ring than another node M.
> (The reason we need to use the range for this instead of load, is load may
> include an arbitrary amount of data that no longer belongs to the node,
> pending removal by cleanup.)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
