[CASSANDRA-13526] nodetool cleanup on KS with no replicas should remove old data, not silently complete

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 3.0.16, 3.11.2, 4.0-alpha1, 4.0
• Component/s: Local/Compaction
• Labels: usability
• Severity: Normal
• Assignee: Zhao Yang
• Reporter: Jeff Jirsa

Authors

Zhao Yang

Reviewers

Jeff Jirsa

• Created: 11/May/17 20:11
• Updated: 15/May/20 08:01
• Resolved: 07/Dec/17 05:51

Description

From the user list:

https://lists.apache.org/thread.html/5d49cc6bbc6fd2e5f8b12f2308a3e24212a55afbb441af5cb8cd4167@%3Cuser.cassandra.apache.org%3E

If you have a multi-dc cluster, but some keyspaces not replicated to a given DC, you'll be unable to run cleanup on those keyspaces in that DC, because the cleanup code will see no ranges and exit early

Issue Links

• is caused by: CASSANDRA-10991 Cleanup OpsCenter keyspace fails - node thinks that didn't joined the ring yet
• is duplicated by: CASSANDRA-10047 nodetool aborts when attempting to cleanup a keyspace with no ranges
• supercedes: CASSANDRA-9652 Nodetool cleanup does not work for nodes taken out of replication
• links to: GitHub Pull Request #1