cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peter Schuller (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CASSANDRA-2674) accidental 'recommission' is too easy
Date Fri, 20 May 2011 08:21:48 GMT

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

Peter Schuller resolved CASSANDRA-2674.
---------------------------------------

    Resolution: Invalid

Please ignore - auto_bootstrap was false (how ironic...).

> accidental 'recommission' is too easy
> -------------------------------------
>
>                 Key: CASSANDRA-2674
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2674
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Peter Schuller
>            Priority: Minor
>
> (tested on 0.7.5, but I have no reason to believe it's specific)
> After decommission, simply restarting the node causes it to pop back into the cluster
as Up/Normal without ceremony or streaming, violating consistency in the cluster. This was
with autobootstrap enabled in the configuration, and I triggered it specifically for the purpose
of testing it, but since the intent was to have that always be turned on anyway (as per CASSANDRA-2447)
this is a problem given how easy it is for a node to get started again after a long-running
'decommission' is started. (E.g., host reboots, whatever.)

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message