cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "MaHaiyang (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-4061) Decommission should take a token
Date Tue, 20 Mar 2012 12:25:40 GMT

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

MaHaiyang commented on CASSANDRA-4061:
--------------------------------------

I think using "./nodetool -h host -p port decommission " is  more simple than using "./nodetool
-h host -p port decommision <the node's token>" . If "./nodetool -h host -p port decommision
<the node's token>"  could be available ,it  can't be better.
                
> 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.2
>
>
> 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

        

Mime
View raw message