cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Ogden (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-8917) Upgrading from 2.0.9 to 2.1.3 with 3 nodes, CL = quorum causes exceptions
Date Fri, 06 Mar 2015 15:08:38 GMT


Gary Ogden commented on CASSANDRA-8917:

We had one node defined as the seed node, which was node 1. 

When we turned off node 3 to update the packages, we didn't get the quorum issue. It was only
when we turned on node3 with 2.1.3 and started the sstable upgrade did we start seeing the
quorum issue.

Is it possible that node1 was unavailable since it was streaming to node 3? And therefore
only node2 was the only node available?

> Upgrading from 2.0.9 to 2.1.3 with 3 nodes, CL = quorum causes exceptions
> -------------------------------------------------------------------------
>                 Key: CASSANDRA-8917
>                 URL:
>             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,
> 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

View raw message