[
https://issues.apache.org/jira/browse/CASSANDRA-2217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis updated CASSANDRA-2217:
--------------------------------------
Attachment: 2217-v7.txt
v7 ScrubTest makes sure that the corrupt data file, actually is. Also modified
scrub to not flush before snapshotting, and fixed rebase over the keyspace
validation patch.
It looks like 0001 patch is missing the data file for ScrubTest though?
Also: is there a reason testScrubeOne/MultiRow are commented out? If so we
should move them to another test class so they don't cause conflicts rather
than cutting them.
> nodetool scrub
> --------------
>
> Key: CASSANDRA-2217
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2217
> Project: Cassandra
> Issue Type: Bug
> Components: Tools
> Reporter: Jonathan Ellis
> Assignee: Jonathan Ellis
> Fix For: 0.7.3
>
> Attachments:
> 0001-CASSANDRA-2217-nodetool-scrub-with-broken-sstable-test.txt, 2217-v2.txt,
> 2217-v3.txt, 2217-v4.txt, 2217-v5.txt, 2217-v7.txt, 2217.txt
>
>
> this is the force-deserialization tool to repair CASSANDRA-2211 and
> CASSANDRA-2216.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
