[
https://issues.apache.org/jira/browse/CASSANDRA-4125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13410899#comment-13410899
]
Brandon Williams commented on CASSANDRA-4125:
---------------------------------------------
bq. Did it support a -a argument at some point?
I don't think so, but it's in the description and might be a good idea, since
people used to pre-vnode cassandra might be a bit shocked when thousands of
lines scroll by when running it :)
bq. I'm of the opinion that it doesn't make sense to visualize the ring
anymore. Perhaps it would be enough to incorporate some sort of per-DC
ownership display into clusterinfo.
I was thinking more of upgrades that aren't on vnodes yet. If you want to move
a node, you need ring to get the token. If you want to remove a node, you need
clusterinfo to get the hostid. And then if you want to know dc/rack info,
you're back to ring (even with vnodes, except now you get scrollshocked.) It
just seems like it'd be nice to get all the info you need from one place, the
way ring currently works.
> Update nodetool for vnodes
> --------------------------
>
> Key: CASSANDRA-4125
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4125
> 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|https://github.com/acunu/cassandra/compare/top-bases/p/4125/01_admin_tools...p/4125/01_admin_tools]|[01_admin_tools.patch|https://github.com/acunu/cassandra/compare/top-bases/p/4125/01_admin_tools...p/4125/01_admin_tools.diff]|Updated
> nodetool|
> ----
> _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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
