Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 11 Aug 2015 20:26:46 +0000 (UTC)
From: "Russell Bradberry (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12854260.1439324494000.36746.1439324806154@Atlassian.JIRA>
In-Reply-To: <JIRA.12854260.1439324494000@Atlassian.JIRA>
References: <JIRA.12854260.1439324494000@Atlassian.JIRA>
 <JIRA.12854260.1439324494634@arcas>
Subject: [jira] [Updated] (CASSANDRA-10047) nodetool aborts when attempting
 to cleanup a keyspace with no ranges
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CASSANDRA-10047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Russell Bradberry updated CASSANDRA-10047:
------------------------------------------
    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:

{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.

  was:
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.


> 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:
> {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.3.4#6332)