Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Wed, 26 Mar 2014 16:36:16 +0000 (UTC)
From: "Tyler Hobbs (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12703555.1395773813955.9414.1395851776240@arcas>
In-Reply-To: <JIRA.12703555.1395773813955@arcas>
References: <JIRA.12703555.1395773813955@arcas>
Subject: [jira] [Commented] (CASSANDRA-6924) Data Inserted Immediately After
 Secondary Index Creation is not Indexed
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CASSANDRA-6924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13948070#comment-13948070 ] 

Tyler Hobbs commented on CASSANDRA-6924:
----------------------------------------

bq. How reliable is the test failure on your box? I just tried said test (5 times so far) without reproducing the failure.

When run against a three-node ccm cluster, it fails about 80% of the time.  I'll run a bisect to pinpoint the cause.

> Data Inserted Immediately After Secondary Index Creation is not Indexed
> -----------------------------------------------------------------------
>
>                 Key: CASSANDRA-6924
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6924
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Tyler Hobbs
>             Fix For: 1.2.16
>
>
> The head of the cassandra-1.2 branch (currently 1.2.16-tentative) contains a regression from 1.2.15.  Data that is inserted immediately after secondary index creation may never get indexed.
> You can reproduce the issue with a [pycassa integration test|https://github.com/pycassa/pycassa/blob/master/tests/test_autopacking.py#L793] by running:
> {noformat}
> nosetests tests/test_autopacking.py:TestKeyValidators.test_get_indexed_slices
> {noformat}
> from the pycassa directory.
> The operation order goes like this:
> # create CF
> # create secondary index
> # insert data
> # query secondary index
> If a short sleep is added in between steps 2 and 3, the data gets indexed and the query is successful.
> If a sleep is only added in between steps 3 and 4, some of the data is never indexed and the query will return incomplete results.  This appears to be the case even if the sleep is relatively long (30s), which makes me think the data may never get indexed.


--
This message was sent by Atlassian JIRA
(v6.2#6252)