[
https://issues.apache.org/jira/browse/CASSANDRA-10047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16287156#comment-16287156
]
Jeff Jirsa commented on CASSANDRA-10047:
----------------------------------------
I think this is the original of CASSANDRA-13526, but CASSANDRA-13526 had a
patch, so I believe this is done. Closing, please re-open if I'm wrong.
> nodetool aborts when attempting to cleanup a keyspace with no ranges
> --------------------------------------------------------------------
>
> Key: CASSANDRA-10047
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10047
> Project: Cassandra
> Issue Type: Bug
> Environment: 2.1.8
> Reporter: Russell Bradberry
> Priority: Minor
>
> 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:
> {code}
> 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)
> {code}
> The error messages in the logs are :
> {code}
> CompactionManager.java:370 - Cleanup cannot run before a node has joined the
> ring
> {code}
> 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.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
