[
https://issues.apache.org/jira/browse/CASSANDRA-5791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14619194#comment-14619194
]
Jonathan Ellis commented on CASSANDRA-5791:
-------------------------------------------
More minor point:
I'm not sure that keeping "extended verify" code around is worth it. Since the
point is to work around not having a checksum, we could just scrub instead.
This is slightly more heavyweight but it would be a one-time cost (scrub would
build a new checksum) and we wouldn't have to worry about keeping two versions
of almost-the-same-code in sync.
> A nodetool command to validate all sstables in a node
> -----------------------------------------------------
>
> Key: CASSANDRA-5791
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5791
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Reporter: sankalp kohli
> Assignee: Jeff Jirsa
> Priority: Minor
> Fix For: 2.2.0 beta 1
>
> Attachments: cassandra-5791-20150319.diff,
> cassandra-5791-patch-3.diff, cassandra-5791.patch-2
>
>
> CUrrently there is no nodetool command to validate all sstables on disk. The
> only way to do this is to run a repair and see if it succeeds. But we cannot
> repair the system keyspace.
> Also we can run upgrade sstables but that re writes all the sstables.
> This command should check the hash of all sstables and return whether all
> data is readable all not. This should NOT care about consistency.
> The compressed sstables do not have hash so not sure how it will work there.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
