[
https://issues.apache.org/jira/browse/CASSANDRA-10905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15110470#comment-15110470
]
Sam Tunnicliffe commented on CASSANDRA-10905:
---------------------------------------------
The dtest makes an invalid assumption that a specific node will act as
coordinator for a particular query. Usually this is true, but occasionally it
may not be, leading to the flapping. [This
PR|https://github.com/riptano/cassandra-dtest/pull/758] fixes the dtest, so
I'll close this once that's merged.
> secondary_indexes_test.py:TestSecondaryIndexes.test_only_coordinator_chooses_index_for_query
> flaps on 3.0+
> ----------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-10905
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10905
> Project: Cassandra
> Issue Type: Sub-task
> Reporter: Jim Witschey
> Assignee: Sam Tunnicliffe
> Fix For: 3.0.x
>
>
> This test flaps when it expects to find 1 of each of several trace events,
> but doesn't find some of them. I noticed it on 3.0:
> http://cassci.datastax.com/job/cassandra-3.0_dtest/438/testReport/junit/secondary_indexes_test/TestSecondaryIndexes/test_only_coordinator_chooses_index_for_query/history/
> But I've also seen it on trunk, so it would appear it hasn't been fixed:
> http://cassci.datastax.com/job/trunk_dtest/831/testReport/junit/secondary_indexes_test/TestSecondaryIndexes/test_only_coordinator_chooses_index_for_query/
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
