I am trying to add a new node to an existing cluster. When I start cassandra on the new node I am seeing the below error.
ERROR [main] 2024-11-27 17:04:13,039 CassandraDaemon.java:759 - Exception encountered during startup
java.lang.IllegalStateException: No sources found for (6583315391450457888,6586615426701824871]
Has anyone had this before or have any suggestions on what this could mean?
Thanks
I am trying to add a new node to an existing cluster. When I start cassandra on the new node I am seeing the below error.
ERROR [main] 2024-11-27 17:04:13,039 CassandraDaemon.java:759 - Exception encountered during startup
java.lang.IllegalStateException: No sources found for (6583315391450457888,6586615426701824871]
Has anyone had this before or have any suggestions on what this could mean?
Thanks
Share Improve this question edited Jan 14 at 6:48 Erick Ramirez 16.4k2 gold badges21 silver badges31 bronze badges asked Nov 28, 2024 at 8:53 LensterLenster 431 silver badge4 bronze badges 1- Thanks for posting on Stack Overflow! A friendly reminder that this site is for getting help with coding, algorithm, or programming language problems so I voted to have your post moved to DBA Stack Exchange. For future reference, you should post DB admin/ops questions on dba.stackexchange/questions/ask?tags=cassandra. Cheers! – Erick Ramirez Commented Jan 16 at 2:50
2 Answers
Reset to default 1Most likely you have a keyspace that is replicating to a data center that doesnt exist. When it starts bootstrapping its looking to stream data from it but it cant find any nodes. Type describe schema
in cqlsh on a different node and look for the CREATE KEYSPACE
lines and go over them. It is case sensitive so look carefully.
To add to @Chris Lohfink's answer, the new node is trying to bootstrap itself by requesting data from other replicas. However, it can't find a replica that has the data for the given token range so it reports it as an IllegalStateException
.
You commented that you changed the replication of some keyspaces and decommissioned a node. There is a good chance that one (or more) keyspaces are misconfigured so the new node is not able to find a replica and it's almost always a keyspace replicated to a non-existent DC.
As a friendly note, you are more likely to get help if you make it easy for someone else by providing as much relevant detail as possible. The common things you should include specific to your issue are:
- full error message PLUS full stack trace
- Cassandra version
If you're interested, I've written a guide to asking good questions on the official Apache Cassandra website.
If you update your original post with the output of nodetool status
from one of the nodes and all the CREATE KEYSPACE
definitions from the schema, I'd be happy to review them and provide additional pointers. Cheers!