Thank you Michael.
Well, this was apparently my bad.
1. nodetool connects to the local JMX port 7199, which is indeed running on
localhost in my case.
2. I did a few more attempts, the message "Aborted cleaning up atleast one
column family in keyspace " only appears in the DC where
is not
By default, yes, nodetool connects to localhost, which your log entries
show. Use `nodetool -h $PRIV_IP cleanup ...` to connect to that private
IP it's listening on. `nodetool help cleanup` for all options.
--
Kind regards,
Michael
On 02/10/2017 02:22 PM, Simone Franzini wrote:
> I am running
I am running DSE 4.8.7 / Cassandra 2.1.14.
When I attempt to run nodetool cleanup on any node / any environment we are
managing, I get the following output:
Aborted cleaning up atleast one column family in keyspace ,
check server logs for more information.
error: nodetool failed, check server
Hi,
Thanks for the reply. Since nodetool cleanup is not working even after
upgrading to 2.0.13, is it recommended to go to an older version (2.0.11 for
example, with 2.0.12 also it did not work). Is there any other way of cleaning
data from existing nodes after adding a new node.
Regards,
It should work on 2.0.13. If it fails with that assertion, you should just
retry. If that does not work, and you can reproduce this, please file a
ticket
/Marcus
On Tue, Mar 31, 2015 at 9:33 AM, Amlan Roy amlan@cleartrip.com wrote:
Hi,
Thanks for the reply. Since nodetool cleanup is not
Hi,
I have added new nodes to an existing cluster and ran the “nodetool cleanup”. I
am getting the following error. Wanted to know if there is any solution to it.
Regards,
Amlan
Error occurred during cleanup
java.util.concurrent.ExecutionException: java.lang.AssertionError: Memory was
freed
Hi Amlan,
On 30/03/15 22:12, Amlan Roy wrote:
Hi,
I have added new nodes to an existing cluster and ran the “nodetool cleanup”. I
am getting the following error. Wanted to know if there is any solution to it.
Regards,
Amlan
Error occurred during cleanup
Code problem that was patched in
https://issues.apache.org/jira/browse/CASSANDRA-8716
https://issues.apache.org/jira/browse/CASSANDRA-8716. Upgrade to 2.0.13
On Mar 30, 2015, at 1:12 PM, Amlan Roy amlan@cleartrip.com wrote:
Hi,
I have added new nodes to an existing cluster and ran
On Mon, Mar 30, 2015 at 4:21 PM, Amlan Roy amlan@cleartrip.com wrote:
Thanks for the reply. I have upgraded to 2.0.13. Now I get the following
error.
If cleanup is still excepting for you on 2.0.13 with some sstables you
have, I would strongly consider :
1) file a JIRA
Hi,
Thanks for the reply. I have upgraded to 2.0.13. Now I get the following error.
Regards,
Amlan
Exception in thread main java.lang.AssertionError:
[SSTableReader(path='/data/1/cassandra/data/xxx/xxx/xxx.db'),
SSTableReader(path='/data/1/cassandra/data/xxx/xxx/xxx.db')]
at
Looks like the issue is https://issues.apache.org/jira/browse/CASSANDRA-9070.
On Mon, Mar 30, 2015 at 6:25 PM, Robert Coli rc...@eventbrite.com wrote:
On Mon, Mar 30, 2015 at 4:21 PM, Amlan Roy amlan@cleartrip.com wrote:
Thanks for the reply. I have upgraded to 2.0.13. Now I get the
After joining a node to an existing cluster, I run 'nodetool cleanup'
as recommended on existing nodes in the cluster. On one node, after
some time, I am getting an error starting with
Exception in thread main java.lang.AssertionError:
12 matches
Mail list logo
