cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tyler Hobbs (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-6924) Data Inserted Immediately After Secondary Index Creation is not Indexed
Date Wed, 26 Mar 2014 16:36:16 GMT


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:
>             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
> You can reproduce the issue with a [pycassa integration test|]
by running:
> {noformat}
> nosetests tests/
> {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

View raw message