cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yaniv Kunda (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-2217) nodetool scrub
Date Thu, 24 Feb 2011 13:14:40 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-2217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12998837#comment-12998837
] 

Yaniv Kunda commented on CASSANDRA-2217:
----------------------------------------

Nope - have always been using RandomPartioner.
I was running 0.7.2 when I encountered the bug, and updated to 2011-02-24_02-21-51 from hudson
to use the fixed nodetool scrub -
but I didn't change configuration, just copied cassandra.yaml.

> 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

        

Mime
View raw message