You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Russell Bradberry (JIRA)" <ji...@apache.org> on 2015/08/11 22:21:46 UTC

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

Russell Bradberry created CASSANDRA-10047:
---------------------------------------------

             Summary: 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
          Components: Core
         Environment: 2.1.8
            Reporter: Russell Bradberry
            Priority: Critical


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:



{{root@analytics-004:~# nodetool cleanup}}
{{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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)