cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Ogden (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-8917) Upgrading from 2.0.9 to 2.1.3 with 3 nodes, CL = quorum causes exceptions
Date Thu, 19 Mar 2015 13:35:39 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-8917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14369321#comment-14369321
] 

Gary Ogden commented on CASSANDRA-8917:
---------------------------------------

We only have one node designated as the seed node. Should we increase that to two? Would that
be a potential cause of this issue?

> 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-cassandra.yaml, node1-system.log,
node2-cassandra.yaml, node2-system.log, node3-cassandra.yaml, 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)

Mime
View raw message