[ https://issues.apache.org/jira/browse/CASSANDRA-8917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Ogden updated CASSANDRA-8917: ---------------------------------- Attachment: node3-system.log node2-system.log node1-system.log jersey_error.log b_output.log b_output and jersey_error are the stacktrace errors from glassfish. The other 3 files are from each of the 3 nodes during the time period of the upgrade and rollback to 2.0.9. node 3 was the node we were attempting the upgrade on (10.6.71.198 in the logs) > 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)