[
https://issues.apache.org/jira/browse/CASSANDRA-8917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14351253#comment-14351253
]
Gary Ogden edited comment on CASSANDRA-8917 at 3/7/15 1:04 AM:
---------------------------------------------------------------
That's when we decided to remove the node and revert back to 2.0.9. That's 3
hours after we started seeing the problems. If you look at the b_output.log
you'll see the errors were well before our decision to remove the node, install
2.0.9 and then add the node to the cluster.
was (Author: ogg1e):
That's when we decided to remove the node and revert back to 2.0.9. That's 3
hours after we started seeing the problems. If you look at the b_output.log
you'll see the errors we well before our decision to remove the node, install
2.0.9 and then add the node to the cluster.
> Upgrading from 2.0.9 to 2.1.3 with 3 nodes, CL = quorum causes exceptions
> -------------------------------------------------------------------------
>
> Key: CASSANDRA-8917
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8917
> Project: Cassandra
> Issue Type: Bug
> Environment: C* 2.0.9, Centos 6.5, Java 1.7.0_72, spring data
> cassandra 1.1.1, cassandra java driver 2.0.9
> Reporter: Gary Ogden
> Attachments: b_output.log, jersey_error.log, node1-system.log,
> node2-system.log, node3-system.log
>
>
> We have java apps running on glassfish that read/write to our 3 node cluster
> running on 2.0.9.
> we have the CL set to quorum for all reads and writes.
> When we started to upgrade the first node and did the sstable upgrade on that
> node, we started getting this error on reads and writes:
> com.datastax.driver.core.exceptions.UnavailableException: Not enough replica
> available for query at consistency QUORUM (2 required but only 1 alive)
> How is that possible when we have 3 nodes total, and there was 2 that were up
> and it's saying we can't get the required CL?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
