cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeremy Hanna (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-10535) Solidify use of Decommission command
Date Mon, 26 Oct 2015 18:43:27 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-10535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jeremy Hanna updated CASSANDRA-10535:
-------------------------------------
    Summary: Solidify use of Decommission command  (was: Solidify use of Demmission command)

> Solidify use of Decommission command
> ------------------------------------
>
>                 Key: CASSANDRA-10535
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10535
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Tools
>         Environment: All C* environments
>            Reporter: Richard Lewis
>             Fix For: 3.x, 2.1.x
>
>
> Decommission should have protection mechanisms so nodes are not accidentally removed
from a cluster due to error input.
> 1) Decommission should have a validation message "Do you really want to do this"
> 2) Decommission should be run from a remote node.
> Background, user was on the wrong node, ran decommission, which required no validation
which resulted in the node being removed from the cluster accidentally.  There should be validation
required so a critical command such as this is not accidentally run.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message