Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Fri, 10 Apr 2015 18:10:15 +0000 (UTC)
From: "Sam Tunnicliffe (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12786325.1427488475000.56240.1428689415231@Atlassian.JIRA>
In-Reply-To: <JIRA.12786325.1427488475000@Atlassian.JIRA>
References: <JIRA.12786325.1427488475000@Atlassian.JIRA>
 <JIRA.12786325.1427488475155@arcas>
Subject: [jira] [Updated] (CASSANDRA-9062) Investigate failing collection
 indexing dtests
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CASSANDRA-9062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sam Tunnicliffe updated CASSANDRA-9062:
---------------------------------------
    Reviewer: Benedict

> Investigate failing collection indexing dtests
> ----------------------------------------------
>
>                 Key: CASSANDRA-9062
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9062
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Tests
>            Reporter: Tyler Hobbs
>            Assignee: Sam Tunnicliffe
>             Fix For: 3.0
>
>         Attachments: 9062.txt
>
>
> There are frequent failures with the dtests related to indexing collections ({{secondary_indexes_test.py:TestSecondaryIndexesOnCollections}}).
> I tried to look into the reason for failure.  The test does seem to be correct, because it can occasionally pass.  It seems like the failures are due to indexing lagging behind the inserts, resulting in a partial set of results when the index is queried shortly afterwards (getting ~20k matching rows instead of the expected 50k).


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