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

Brandon Williams edited comment on CASSANDRA-4061 at 5/9/12 3:57 PM:
---------------------------------------------------------------------

To the dismay of my OCD, after looking at the options I think calling 
decommission on the host you want to decommission is the cleanest option we 
have.

However, as stated, nodetool should definitely not allow miscellaneous args to 
get passed, allow users to think it's doing something other than what it is.  
Patch to fix this and clarify the help message, against 1.0 in the unlikely 
case we ever have reason to roll a 1.0.11.
                
      was (Author: brandon.williams):
    To the dismay of my OCD, after looking at the options I think calling 
decommission on the host you want to decommission is the cleanest option we 
have.

However, as stated, nodetool should definitely not allow miscellaneous args to 
get passed, allow users to think it's doing something other than what it is.  
Patch to fix this and clarify the help message, against 1.0 in the unlikely 
case we ever have reason to roll a 1.1.11.
                  
> Decommission should take a token
> --------------------------------
>
>                 Key: CASSANDRA-4061
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4061
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Brandon Williams
>            Assignee: Brandon Williams
>             Fix For: 1.0.11
>
>         Attachments: 4061.txt
>
>
> Like removetoken, decom should take a token parameter.  This is a bit easier 
> said than done because it changes gossip, but I've seen enough people burned 
> by this (as I have myself.)  In the short term though *decommission still 
> accepts a token parameter* which I thought we had fixed.

--
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

        

Reply via email to