cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff Jirsa (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-14702) Cassandra Write failed even when the required nodes to Ack(consistency) are up.
Date Thu, 01 Nov 2018 23:42:00 GMT


Jeff Jirsa commented on CASSANDRA-14702:

Something here still doesn't make sense

Either the write was at quorum (but the log says it's not), or the RF is actually >= 4
(not 3), or there was a pending range and blockFor was incremented, or there's some serious
bug here. 

I suspect we're going to have a very hard time figuring out the cause without a lot more logs
or a heap dump or steps to reproduce. 

> Cassandra Write failed even when the required nodes to Ack(consistency) are up.
> -------------------------------------------------------------------------------
>                 Key: CASSANDRA-14702
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Rohit Singh
>            Priority: Blocker
> Hi,
> We have following configuration in our project for cassandra. 
> Total nodes in Cluster-5
> Replication Factor- 3
> Consistency- LOCAL_QUORUM
> We get the writetimeout exception from cassandra even when 2 nodes are up and why does
stack trace says that 3 replica were required when consistency is 2?
> Below is the exception we got:-
> com.datastax.driver.core.exceptions.WriteTimeoutException: Cassandra timeout during write
query at consistency LOCAL_QUORUM (3 replica were required but only 2 acknowledged the write)
>  at com.datastax.driver.core.Responses$Error$1.decode(
>  at com.datastax.driver.core.Responses$Error$1.decode(
>  at com.datastax.driver.core.Message$ProtocolDecoder.decode(
>  at com.datastax.driver.core.Message$ProtocolDecoder.decode(
>  at io.netty.handler.codec.MessageToMessageDecoder.channelRead(

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message