cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Philip Thompson (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-7599) Dtest on low cardinality secondary indexes failing in 2.1
Date Wed, 06 Aug 2014 18:46:15 GMT


Philip Thompson commented on CASSANDRA-7599:

The test has begun failing on 2.1.0 again for the same reason. The end of the trace looks

> Dtest on low cardinality secondary indexes failing in 2.1
> ---------------------------------------------------------
>                 Key: CASSANDRA-7599
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core, Tests
>            Reporter: Shawn Kumar
>            Assignee: Tyler Hobbs
>              Labels: qa-resolved
>             Fix For: 2.1 rc5
>         Attachments: 7599.txt
> test_low_cardinality_indexes in is failing when tested on the
cassandra-2.1 branch. This test has been failing on cassci for a while (at least the last
10 builds) and can easily be reproduced locally as well. It appears to still work on 2.0.
> {code}
> ======================================================================
> FAIL: test_low_cardinality_indexes (secondary_indexes_test.TestSecondaryIndexes)
> ----------------------------------------------------------------------
> Traceback (most recent call last):
>   File "/home/shawn/git/cstar5/cassandra-dtest/", line 213, in wrapped
>     f(obj)
>   File "/home/shawn/git/cstar5/cassandra-dtest/", line 89, in
>     check_request_order()
>   File "/home/shawn/git/cstar5/cassandra-dtest/", line 84, in
>     self.assertTrue('Executing indexed scan' in relevant_events[-1][0], str(relevant_events[-1]))
> AssertionError: (u'Enqueuing request to /', '')
> {code}
> The test checks that a series of messages are found in the trace after a select query
against an index is carried out. It fails to find an 'Executing indexed scan' from node 1
(which takes the query, note both node2 and node3 produced this message). Brief investigation
seemed to show that whichever node you create the patient_cql_connection on will not produce
this message, indicating perhaps it does not carry out the scan.  Should also note that changing
'numrows' (rows initially added) or 'b' (value on index column we query for) does not appear
to make a difference.

This message was sent by Atlassian JIRA

View raw message