[jira] [Updated] (CASSANDRA-5223) Secondary index doesn't get repaired

["Ryan McGuire (JIRA)" <ji...@apache.org>]

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

Ryan McGuire updated CASSANDRA-5223:
------------------------------------

    Labels: qa-resolved  (was: )

> Secondary index doesn't get repaired
> ------------------------------------
>
>                 Key: CASSANDRA-5223
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5223
>             Project: Cassandra
>          Issue Type: Bug
>    Affects Versions: 1.2.1
>         Environment: Ubuntu dtest, laptop with 8G RAM
>            Reporter: Alexei Bakanov
>            Assignee: Ryan McGuire
>              Labels: qa-resolved
>         Attachments: secondary_index_repair_test.py, secondary_index_repair_test_2.py, secondary_index_repair_test_3.py
>
>
> Looks like secondary indexes don't get repaired by any of the Cassandra repair mechanisms for NetworkTopologyStrategy. SimpleStrategy however works fine.
> The issue started as a mail to Cassandra userlist: http://article.gmane.org/gmane.comp.db.cassandra.user/30909
> I striped reproduction recipe down and made a d-test which inserts two rows into a cluster of two nodes, where the first node goes down after the first insert and goes back up after the second insert. Secondary index doesn't get repaired by neither hinted-handoff, read repair, nor manual 'repair' operation which the d-test triggers before reading the data.
> Moreover the second row is not visible in the index unless I do CL.ALL read or drop/create the index.



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