Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Wed, 8 Jul 2015 00:09:04 +0000 (UTC)
From: "Aleksey Yeschenko (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12842994.1436217140000.124626.1436314144888@Atlassian.JIRA>
In-Reply-To: <JIRA.12842994.1436217140000@Atlassian.JIRA>
References: <JIRA.12842994.1436217140000@Atlassian.JIRA>
 <JIRA.12842994.1436217140640@arcas>
Subject: [jira] [Commented] (CASSANDRA-9742) Nodetool verify
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Aleksey Yeschenko commented on CASSANDRA-9742:
----------------------------------------------

I still disagree, but not strongly enough to argue. Hints checksums weaken the argument for a single command somewhat, but maybe we just want a separate command for hints (or just not care about them at all for now).

> Nodetool verify
> ---------------
>
>                 Key: CASSANDRA-9742
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9742
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Tools
>            Reporter: Jonathan Ellis
>             Fix For: 3.x
>
>
> We introduced incremental repair in 2.1 but it is difficult to make that the default without unpleasant surprises for incautious users.
> Additionally, while we now store sstable checksums, we leave verification to the user.
> I propose introducing a new command, {{nodetool verify}}, that would address both of these.
> Default operation would be to do an incremental repair, plus validate checksums on *all* sstables (not just unrepaired ones).  We could also have --local mode (checksums only) and --full (classic repair).


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