cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefania (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-5174) expose nodetool scrub for 2Is
Date Thu, 12 Mar 2015 09:59:38 GMT


Stefania commented on CASSANDRA-5174:

Hello [~jbellis], a few questions:
# When scrubbing a non-index cf do we want to automatically scrub the associated secondary
index cfs?
# When we detect corruption whilst scrubbing an index cf, should we abort and rebuild the
index regardless of the skipCorrupted parameter?
# Do we block the nodetool client until the index is rebuilt in case of failure or do we let
it run asynchronously?
# Do we need to support the standalone scrubber as well?

> expose nodetool scrub for 2Is
> -----------------------------
>                 Key: CASSANDRA-5174
>                 URL:
>             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

View raw message