-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unavailable exception #29
Comments
Hey @trK54Ylmz , how is your keyspace set up? Do you have a high replication factor and not all shards available? |
Hi @LarsFronius , I get the same problem :
I have single node hosted on AWS; My test keyspace is : Any suggestions how to fix it? Should I reduce the replication factor ? |
With a single node, there is no way to fulfil your replication_factor of 3 replicas, so Cassandra throws back that the keyspace is unavailable, which is what you see - the Error data array though is quite misleading. |
Thanks @LarsFronius that helped! |
@LarsFronius Thanks that helped me too. @evseevnn My problem solved. It was my test keyspace and replication_factor was set to 3. But,
in my opinion the error message should be better than this |
Here is my code. I think there is a encoding/decoding or response parse problem.
And exception message is:
CQL shell output:
and finally stack trace
The text was updated successfully, but these errors were encountered: