[
https://issues.apache.org/jira/browse/CASSANDRA-9742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14623529#comment-14623529
]
Aleksey Yeschenko commented on CASSANDRA-9742:
----------------------------------------------
bq. But you'd still want to schedule a repair on hint checksum failure, right?
Just on target node instead of local.
Yes, you'd still want to, if only for batchlog reasons. Not having any hints
checksum failures doesn't mean you *don't* want to schedule repair, though. I
don't want users to be confused.
> 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)
