cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andy Cobley (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-5954) Make nodetool ring print an error message and suggest nodetool status when vnodes are enabled
Date Fri, 30 Aug 2013 07:57:52 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-5954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13754478#comment-13754478
] 

Andy Cobley commented on CASSANDRA-5954:
----------------------------------------

Can we be careful with this change ?  I'm thinking there may be scripts out there that rely
on the current behavior that may break if you change it (does opcenter use nodetool for its
operations ?).  It seems to me the original suggestion is because nodetool ring is not the
best way to monitor vnodes and user education is needed on the role of nodetool status.

With that in mind, would it be better to simply add a message at the bottom of the output
of nodetool ring with vnodes suggesting nodetool status ?  That should minimise any script
problems as they should just ignore the last line ?
                
> Make nodetool ring print an error message and suggest nodetool status when vnodes are
enabled
> ---------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-5954
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5954
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Tools
>            Reporter: Jonathan Ellis
>            Assignee: Lyuben Todorov
>            Priority: Minor
>             Fix For: 2.0.1
>
>


--
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: http://www.atlassian.com/software/jira

Mime
View raw message