cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefania (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-12092) dtest failure in consistency_test.TestAccuracy.test_simple_strategy_counters
Date Fri, 19 Aug 2016 10:13:21 GMT


Stefania commented on CASSANDRA-12092:

I was able to reproduce one [failure|]
with debug logs finally, see [^jenkins-stef1927-dtest-multiplex-23_logs.000.tar.gz] attached.

It seems that when the test fails, a digest arrives before the local read completes at CL
ONE, and this triggers async repair due to the digest mismatch if the other node has a different
counter value, which is expected. However, I haven't understood why none of the two nodes
returns the up-to-date counter from the local data response, since at least one of them should
have applied the mutation that it received from the leader - given that we write at CL.QUORUM.
So I'm still investigating.

> dtest failure in consistency_test.TestAccuracy.test_simple_strategy_counters
> ----------------------------------------------------------------------------
>                 Key: CASSANDRA-12092
>                 URL:
>             Project: Cassandra
>          Issue Type: Test
>            Reporter: Sean McCarthy
>            Assignee: Stefania
>              Labels: dtest
>         Attachments: jenkins-stef1927-dtest-multiplex-23_logs.000.tar.gz, node1.log,
node2.log, node3.log
> example failure:
> Failed on CassCI build cassandra-2.1_dtest #484
> {code}
> Standard Error
> Traceback (most recent call last):
>   File "/home/automaton/cassandra-dtest/", line 514, in run
>     valid_fcn(v)
>   File "/home/automaton/cassandra-dtest/", line 497, in validate_counters
>     check_all_sessions(s, n, c)
>   File "/home/automaton/cassandra-dtest/", line 490, in check_all_sessions
>     "value of %s at key %d, instead got these values: %s" % (write_nodes, val, n, results)
> AssertionError: Failed to read value from sufficient number of nodes, required 2 nodes
to have a counter value of 1 at key 200, instead got these values: [0, 0, 1]
> {code}

This message was sent by Atlassian JIRA

View raw message