Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Wed, 17 Apr 2013 08:37:17 +0000 (UTC)
From: "Jonathan Ellis (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12630876.1360071596897.179313.1366187837931@arcas>
In-Reply-To: <JIRA.12630876.1360071596897@arcas>
References: <JIRA.12630876.1360071596897@arcas>
Subject: [jira] [Resolved] (CASSANDRA-5223) Secondary index doesn't get
 repaired
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jonathan Ellis resolved CASSANDRA-5223.
---------------------------------------

    Resolution: Cannot Reproduce
    
> 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
>         Attachments: secondary_index_repair_test_2.py, secondary_index_repair_test_3.py, secondary_index_repair_test.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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira