Vote count:
0
Over the weekend, we started seeing errors in Cassandra. Essentially, complaining that it couldn't get enough nodes together for SERIAL consistency.
This appeared to be a problem with AWS vpn across regions. So, to simplify, I dropped one the other node (There were only two nodes at the time). I did this by removing the seed from the last remaining node's cassandra.yaml:
seed_provider:
...
- seeds: "single node ip"
I also ran nodetool removenode on the old node (which was showing a dead state).
So the topology is dead simple. Application is a Java app which connects to the Cassandra node via Java API.
Below is the error I am seeing now:
Caused by: com.datastax.driver.core.exceptions.UnavailableException: Not enough replica available for query at consistency QUORUM (2 required but only 1 alive)
at com.datastax.driver.core.Responses$Error$1.decode(Responses.java:45)
at com.datastax.driver.core.Responses$Error$1.decode(Responses.java:34)
at com.datastax.driver.core.Message$ProtocolDecoder.decode(Message.java:182)
at org.jboss.netty.handler.codec.oneone.OneToOneDecoder.handleUpstream(OneToOneDecoder.java:66)
... 21 more
Which is the exact same error as before, except node we have QUORUM where we had SERIAL before.
asked 1 min ago
Cassandra: Not enough replica
Aucun commentaire:
Enregistrer un commentaire