[CASSANDRA-10047] nodetool aborts when attempting to cleanup a keyspace with no ranges

• Type: Bug
• Status: Resolved
• Priority: Low
• Resolution: Duplicate

Environment

2.1.8

• Severity: Low
• Assignee: Unassigned
• Reporter: Russell Bradberry
• Created: 11/Aug/15 20:21
• Updated: 16/Apr/19 09:31
• Resolved: 12/Dec/17 05:43

Description

When running nodetool cleanup in a DC that has no ranges for a keyspace, nodetool will abort with the following message when attempting to cleanup that keyspace:

Aborted cleaning up atleast one column family in keyspace ks, check server logs for more information.
error: nodetool failed, check server logs
-- StackTrace --
java.lang.RuntimeException: nodetool failed, check server logs
	at org.apache.cassandra.tools.NodeTool$NodeToolCmd.run(NodeTool.java:290)
	at org.apache.cassandra.tools.NodeTool.main(NodeTool.java:202)

The error messages in the logs are :

CompactionManager.java:370 - Cleanup cannot run before a node has joined the ring

This behavior prevents subsequent keyspaces from getting cleaned up. The error message is also misleading as it suggests that the only reason a node may not have ranges for a keyspace is because it has yet to join the ring.

Issue Links

• duplicates: CASSANDRA-13526 nodetool cleanup on KS with no replicas should remove old data, not silently complete