Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Wed, 6 Apr 2016 13:27:25 +0000 (UTC)
From: "Jorge Bay (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12854119.1439286015000.150069.1459949245489@Atlassian.JIRA>
In-Reply-To: <JIRA.12854119.1439286015000@Atlassian.JIRA>
References: <JIRA.12854119.1439286015000@Atlassian.JIRA>
 <JIRA.12854119.1439286015926@arcas>
Subject: [jira] [Commented] (CASSANDRA-10041) "timeout during write query at
 consistency ONE" when updating counter at consistency QUORUM and 2 of 3
 nodes alive
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jorge Bay commented on CASSANDRA-10041:
---------------------------------------

I was able to reproduce it with 3.0.x:

{code}
ccm create test -n 3 -b -s -v 3.0.4
ccm node1 cqlsh

CREATE KEYSPACE ks1 WITH replication = {'class': 'SimpleStrategy', 'replication_factor' : 3};
USE ks1;
CREATE TABLE tbl1 (id int PRIMARY KEY, c counter);
CONSISTENCY QUORUM
UPDATE tbl1 SET c = c + 1 WHERE id = 1;
exit

ccm node2 pause
ccm node1 cqlsh

USE ks1
CONSISTENCY QUORUM
UPDATE tbl1 SET c = c + 1 WHERE id = 1;
{code}

> "timeout during write query at consistency ONE" when updating counter at consistency QUORUM and 2 of 3 nodes alive
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-10041
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10041
>             Project: Cassandra
>          Issue Type: Bug
>         Environment: centos 6.6 server, java version "1.8.0_45", cassandra 2.1.8, 3 machines, keyspace with replication factor 3
>            Reporter: Anton Lebedevich
>            Assignee: Sylvestor George
>             Fix For: 2.1.x
>
>
> Test scenario is: kill -9 one node, wait 60 seconds, start it back, wait till it becomes available, wait 120 seconds (during that time all 3 nodes are up), repeat with the next node. Application reads from one table and updates counters in another table with consistency QUORUM. When one node out of 3 is killed application logs this exception for several seconds:
> {noformat}
> Caused by: com.datastax.driver.core.exceptions.WriteTimeoutException: Cassandra timeout during write query at consistency ONE (1 replica were required but only 0 acknowledged the write)
>         at com.datastax.driver.core.Responses$Error$1.decode(Responses.java:57) ~[com.datastax.cassandra.cassandra-driver-core-2.1.6.jar:na]
>         at com.datastax.driver.core.Responses$Error$1.decode(Responses.java:37) ~[com.datastax.cassandra.cassandra-driver-core-2.1.6.jar:na]
>         at com.datastax.driver.core.Message$ProtocolDecoder.decode(Message.java:204) ~[com.datastax.cassandra.cassandra-driver-core-2.1.6.jar:na]
>         at com.datastax.driver.core.Message$ProtocolDecoder.decode(Message.java:195) ~[com.datastax.cassandra.cassandra-driver-core-2.1.6.jar:na]
>         at io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:89) [io.netty.netty-codec-4.0.27.Final.jar:4.0.27.Final]
>         ... 13 common frames omitted
> {noformat}


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)