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

Jonathan Ellis reassigned CASSANDRA-5174:
-----------------------------------------

    Assignee: Stefania  (was: Jason Brown)

If we detect corruption when scrubbing an index, we should kick off a rebuild.  
(Presumably this is uncommon enough that being inefficient and rebuilding the 
whole thing is okay.  In any case, I don't see a better option.)

With CASSANDRA-6477 coming this is more important.

> expose nodetool scrub for 2Is
> -----------------------------
>
>                 Key: CASSANDRA-5174
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5174
>             Project: Cassandra
>          Issue Type: Task
>          Components: Core, Tools
>            Reporter: Jason Brown
>            Assignee: Stefania
>            Priority: Minor
>             Fix For: 3.0
>
>
> Continuation of CASSANDRA-4464, where many other nodetool operations were 
> added for 2Is. This ticket supports scrub fo 2Is and is in its own ticket due 
> to the riskiness of deleting data on a bad bug.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to