cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] [Resolved] (CASSANDRA-5223) Secondary index doesn't get repaired
Date Wed, 17 Apr 2013 08:37:17 GMT


Jonathan Ellis resolved CASSANDRA-5223.

    Resolution: Cannot Reproduce
> Secondary index doesn't get repaired
> ------------------------------------
>                 Key: CASSANDRA-5223
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>    Affects Versions: 1.2.1
>         Environment: Ubuntu dtest, laptop with 8G RAM
>            Reporter: Alexei Bakanov
>            Assignee: Ryan McGuire
>         Attachments:,,
> 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:
> 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:

View raw message