Open trK54Ylmz opened 10 years ago
Hey @trK54Ylmz , how is your keyspace set up? Do you have a high replication factor and not all shards available? Its true that we should send a exception that guides you towards this error better. Can you confirm, that this can be the issue?
Hi @LarsFronius ,
I get the same problem :
Fatal error: Uncaught exception 'evseevnn\Cassandra\Exception\CassandraException' with message 'Unavailable exception. Error data: array ( 'consistency' => 2573153, 'node' => 1852731252, 'replica' => 543253352, )'
I have single node hosted on AWS; My test keyspace is :
CREATE KEYSPACE test WITH replication = {'class': 'SimpleStrategy', 'replication_factor': '3'} AND durable_writes = true;
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. With a replication_factor set to 1, you should be fine @bborisov
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,
Unavailable exception. Error data
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