[ https://issues.apache.org/jira/browse/CASSANDRA-9652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15258884#comment-15258884 ]
Thom Valley commented on CASSANDRA-9652: ---------------------------------------- We are seeing this in our POC testing as well (4.8.5 / 2.1.13). All nodes are UN in nodetool status The node in question was "partially" cleaned up. Thinking we might have some funky state issues with host ids. > Nodetool cleanup does not work for nodes taken out of replication > ----------------------------------------------------------------- > > Key: CASSANDRA-9652 > URL: https://issues.apache.org/jira/browse/CASSANDRA-9652 > Project: Cassandra > Issue Type: Bug > Reporter: Erick Ramirez > Fix For: 2.1.x > > > After taking a node (DC) out of replication, running a cleanup does not get > rid of the data on the node. The SSTables remain on disk and no data is > cleared out. > The following entry is recorded in {{system.log}}: > {noformat} > INFO [CompactionExecutor:8] 2015-06-25 12:33:01,417 CompactionManager.java > (line 527) Cleanup cannot run before a node has joined the ring > {noformat} > *STEPS TO REPRODUCE* > # Build a (C* 2.0.10) cluster with multiple DCs. > # Run {{cassandra-stress -n1}} to create schema. > # Alter schema to replicate to all DCs. > {noformat} > cqlsh> ALTER KEYSPACE "Keyspace1" WITH replication = { 'class' : > 'NetworkTopologyStrategy', 'DC1' : 2, 'DC2' : 2, 'DC3' : 1 } ; > {noformat} > # Run {{cassandra-stress -n100000}} to generate data. > # Alter schema to stop replication to {{DC3}}. > # On node in {{DC3}}, run {{nodetool cleanup}}. > *WORKAROUND* > # Stop Cassandra. > # Manually delete the SSTables on disk. > # Start Cassandra. -- This message was sent by Atlassian JIRA (v6.3.4#6332)