cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-4125) Update nodetool for vnodes
Date Wed, 11 Jul 2012 13:38:35 GMT


Brandon Williams commented on CASSANDRA-4125:

bq. Is this because it's one aspect of monitoring / maintaining balance between the nodes?

More as a quick check since, even with vnodes, you can create a large imbalance via fat rows.

bq. Do you think this will be less relevant now?

To some degree, but not completely.

I think new users want to be able to see how much space their cluster is using at a glance,
and foresee a lot of complaints if we remove it at this point.  Also, it's easier to say "send
me your ring output" than "send me the ring output, then the output of info from each node"
and space used is still pertinent information to have, outside of balance issues.

> Update nodetool for vnodes
> --------------------------
>                 Key: CASSANDRA-4125
>                 URL:
>             Project: Cassandra
>          Issue Type: Sub-task
>          Components: Core
>            Reporter: Sam Overton
>            Assignee: Eric Evans
> The proposed changes are intended to preserve backwards compatibility:
> || op || behaviour || deprecated warning?
> | join | Join the ring, use with {{-t}} to join at a specific token, or to add a token
to an existing host |
> | ring | prints the first token for each node, add {{-a}} to print all tokens |
> | move <new token> | if the node only has 1 token then move it. Otherwise die with
an error. | *deprecated*
> | removetoken status/force/<token> | removes the node who owns <token> from
the ring. use {{-t}} option to only remove the token from the node instead of the whole node.
> | describering [keyspace] | show all ranges and their endpoints |
> | getendpoints <keyspace> <cf> <key> | Print the endpoints that own
the key and also their list of tokens |
> _Edit0: Appended patch information._
> h3. Patches
> ||Compare||Raw diff||Description||
> |[01_admin_tools|]|[01_admin_tools.patch|]|Updated
> ----
> _Note: These are branches managed with TopGit. If you are applying the patch output manually,
you will either need to filter the TopGit metadata files (i.e. {{wget -O - <url> | filterdiff
-x*.topdeps -x*.topmsg | patch -p1}}), or remove them afterward ({{rm .topmsg .topdeps}})._

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


View raw message