[
https://issues.apache.org/jira/browse/CASSANDRA-5223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexei Bakanov updated CASSANDRA-5223:
--------------------------------------
Attachment: secondary_index_repair_test_3.py
Hey, looks like this issue is fixed in 1.2.4!
Suspect that CASSANDRA-5397 or CASSANDRA-5179 fixed it. Attaching updated test
file that passes when I run $CASSANDRA_VERSION=1.2.4 nosetests
secondary_index_repair_test_3.py
Great job!
> 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
