[
https://issues.apache.org/jira/browse/CASSANDRA-2428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylvain Lebresne updated CASSANDRA-2428:
----------------------------------------
Attachment: 0001-Don-t-allow-cleanup-when-node-hasn-t-join-the-ring.patch
The ability of not joining on startup is a convenience feature but is honestly
a bit half backed. In particular the token ranges are not set correctly. That's
the reason why cleanup gets an empty list of ranges when querying the local
ranges and thus clean everything.
Attached patch band-aid this by refusing to do a cleanup compaction. I don't
think we want to do more for 0.7. We could make join_ring=false better so that
it sets the ranges based and what's in the system tables, but let's fix the
dangerous behavior first and let that for another ticket.
> Running cleanup on a node with join_ring=false removes all data
> ---------------------------------------------------------------
>
> Key: CASSANDRA-2428
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2428
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.7.1
> Reporter: Chris Goffinet
> Assignee: Sylvain Lebresne
> Priority: Critical
> Fix For: 0.7.5
>
> Attachments:
> 0001-Don-t-allow-cleanup-when-node-hasn-t-join-the-ring.patch
>
>
> If you need to bring up a node with join_ring=false for operator maintenance,
> and this node already has data, it will end up removing the data on the node.
> We noticed this when we were calling cleanup on a specific CF.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
