[
https://issues.apache.org/jira/browse/CASSANDRA-8917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14351181#comment-14351181
]
Tyler Hobbs commented on CASSANDRA-8917:
----------------------------------------
The logs show that a removenode operation was run on node1 for node3:
{noformat}
./node1-system.log:13000: INFO [RMI TCP Connection(507592)-10.6.71.204]
2015-03-04 23:46:25,548 Gossiper.java (line 438) Removing host:
70c2f6c8-bd2a-4229-bf0f-9dd91c7ce823
./node1-system.log-13001- INFO [RMI TCP Connection(507592)-10.6.71.204]
2015-03-04 23:46:25,549 Gossiper.java (line 439) Sleeping for 30000ms to ensure
/10.6.71.198 does not change
{noformat}
There are later logs that show the removal completing. That's almost surely
why you're getting that exception.
> 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)
