[
https://issues.apache.org/jira/browse/CASSANDRA-11225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15217213#comment-15217213
]
Stefania commented on CASSANDRA-11225:
--------------------------------------
There was a problem with the test patch of yesterday, {{query_value()}} now
returns a value, not a boolean. I'm really sorry but we need to repeat the
tests with the fixed patch.
If we still have failures, either our test is too demanding for counters, in
which case we should relax it, perhaps by pausing a few milliseconds, or we may
have a bug hiding somewhere.
Here's what the test does: it reads at CL.ALL to find the current counter
value, it increments the counter at various consistency levels, it checks that
we can read back the incremented counter value from at least the number of
replicas we wrote to, and then it starts all over again but it contacts another
host.
I would expect that a read at CL.ALL would trigger a digest mismatch and a
subsequent repair, so that all nodes start from the same counter value when we
apply the next increment. [~iamaleksey] is this statement correct?
> dtest failure in consistency_test.TestAccuracy.test_simple_strategy_counters
> ----------------------------------------------------------------------------
>
> Key: CASSANDRA-11225
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11225
> Project: Cassandra
> Issue Type: Test
> Reporter: Russ Hatch
> Assignee: Russ Hatch
> Labels: dtest
>
> example failure:
> http://cassci.datastax.com/job/cassandra-2.1_novnode_dtest/209/testReport/consistency_test/TestAccuracy/test_simple_strategy_counters
> Failed on CassCI build cassandra-2.1_novnode_dtest #209
> error: "AssertionError: Failed to read value from sufficient number of nodes,
> required 2 but got 1 - [574, 2]"
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
