cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Srinath Reddy <ksre...@gmail.com>
Subject Re: Error when running nodetool cleanup after adding a new node to a cluster
Date Thu, 09 Feb 2017 05:50:41 GMT
Yes, I ran the nodetool cleanup on the other nodes and got the error.

Thanks.

> On 09-Feb-2017, at 11:12 AM, Harikrishnan Pillai <HPillai@walmartlabs.com> wrote:
> 
> The cleanup has to run on other nodes
> 
> Sent from my iPhone
> 
> On Feb 8, 2017, at 9:14 PM, Srinath Reddy <ksreddy@gmail.com <mailto:ksreddy@gmail.com>>
wrote:
> 
>> Hi,
>> 
>> Trying to re-balacne a Cassandra cluster after adding a new node and I'm getting
this error when running nodetool cleanup. The Cassandra cluster is running in a Kubernetes
cluster.
>> 
>> Cassandra version is 2.2.8
>> 
>> nodetool cleanup
>> error: io.k8s.cassandra.KubernetesSeedProvider
>> Fatal configuration error; unable to start server.  See log for stacktrace.
>> -- StackTrace --
>> org.apache.cassandra.exceptions.ConfigurationException: io.k8s.cassandra.KubernetesSeedProvider
>> Fatal configuration error; unable to start server.  See log for stacktrace.
>> at org.apache.cassandra.config.DatabaseDescriptor.applyConfig(DatabaseDescriptor.java:676)
>> at org.apache.cassandra.config.DatabaseDescriptor.<clinit>(DatabaseDescriptor.java:119)
>> at org.apache.cassandra.tools.NodeProbe.checkJobs(NodeProbe.java:256)
>> at org.apache.cassandra.tools.NodeProbe.forceKeyspaceCleanup(NodeProbe.java:262)
>> at org.apache.cassandra.tools.nodetool.Cleanup.execute(Cleanup.java:55)
>> at org.apache.cassandra.tools.NodeTool$NodeToolCmd.run(NodeTool.java:244)
>> at org.apache.cassandra.tools.NodeTool.main(NodeTool.java:158)
>> 
>> nodetool status
>> Datacenter: datacenter1
>> =======================
>> Status=Up/Down
>> |/ State=Normal/Leaving/Joining/Moving
>> --  Address      Load       Tokens       Owns (effective)  Host ID              
                Rack
>> UN  10.244.3.4   6.91 GB    256          60.8%             bad1c6c6-8c2e-4f0c-9aea-0d63b451e7a1
 rack1
>> UN  10.244.0.3   6.22 GB    256          60.2%             936cb0c0-d14f-4ddd-bfde-3865b922e267
 rack1
>> UN  10.244.1.3   6.12 GB    256          59.4%             0cb43711-b155-449c-83ba-00ed2a97affe
 rack1
>> UN  10.244.4.3   632.43 MB  256          57.8%             55095c75-26df-4180-9004-9fabf88faacc
 rack1
>> UN  10.244.2.10  6.08 GB    256          61.8%             32e32bd2-364f-4b6f-b13a-8814164ed160
 rack1
>> 
>> 
>> Any suggestions on what is needed to re-balance the cluster after adding the new
node? I have run nodetool repair but not able to run nodetool cleanup.
>> 
>> Thanks.
>> 
>> 


Mime
View raw message