You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jeff Jirsa (JIRA)" <ji...@apache.org> on 2017/12/22 20:53:00 UTC
[jira] [Commented] (CASSANDRA-14129) BatchStatement (LOGGED BATCH)
fails: Not enough replica available for query at consistency ONE (1
required but only 0 alive)
[ https://issues.apache.org/jira/browse/CASSANDRA-14129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16301948#comment-16301948 ]
Jeff Jirsa commented on CASSANDRA-14129:
----------------------------------------
The version you note ( 2.0.17 ) is EOL. Have you tried to reproduce this error on a supported version? 2.1.19 being the absolute oldest that's still getting patches?
> BatchStatement (LOGGED BATCH) fails: Not enough replica available for query at consistency ONE (1 required but only 0 alive)
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-14129
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14129
> Project: Cassandra
> Issue Type: Bug
> Reporter: Erik Scheuter
>
> In our test-cluster I get the error "Not enough replica available for query at consistency ONE (1 required but only 0 alive)" when 1 node is down and a BatchStatement is used. By default it uses LOGGED BATCHES and DCAwareRoundRobinPolicy.
> We have 2 DC's, 4 nodes and a RF 2:2. Write Consistency of QUORUM (*not* LOCAL QUORUM).
> I noticed as soon as the driver marked the LocalDC containing the one with the node down, this error occurs. If the other DC is marked as the LocalDC, everything works as expected.
> The issue https://issues.apache.org/jira/browse/CASSANDRA-7870 points to the comment from Olivier Michallat at [StackOverflow|https://stackoverflow.com/questions/26015282/cassandra-not-enough-replica-available-java-driver-behaviour-different-from-c]:
> _This batch log must be replicated to at least one replica other than the coordinator, otherwise that would defeat the above mechanism._
> I think it needs an other replica in the same DC.
> These constraints can lead to downtime, so I expect them to find in the documentation (and a more detailed error message).
> Used:
> Cassandra 2.0.17
> Datastax-driver 3.3.0
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org