You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Caleb Rackliffe (Jira)" <ji...@apache.org> on 2025/12/12 15:26:00 UTC
[jira] [Updated] (CASSANDRA-20949) Optionally verify checksums for SAI on-disk components in nodetool verify
[ https://issues.apache.org/jira/browse/CASSANDRA-20949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Caleb Rackliffe updated CASSANDRA-20949:
----------------------------------------
Reviewers: Caleb Rackliffe, David Capwell (was: Caleb Rackliffe)
> Optionally verify checksums for SAI on-disk components in nodetool verify
> -------------------------------------------------------------------------
>
> Key: CASSANDRA-20949
> URL: https://issues.apache.org/jira/browse/CASSANDRA-20949
> Project: Apache Cassandra
> Issue Type: New Feature
> Components: Feature/SAI, Tool/nodetool
> Reporter: Caleb Rackliffe
> Assignee: Sunil Ramchandra Pawar
> Priority: Normal
> Fix For: 6.x
>
> Time Spent: 3h 10m
> Remaining Estimate: 0h
>
> The *nodetool verify* command has never checked secondary indexes, but with SAI on-disk items being legitimate SSTable components, it might be useful. One place this might come up is when we have some kind of error in streaming. We verify the checksums of SAI components on the receiving end, but not on the sender, and it might be nice to know if there’s a particular corrupted SSTable-attached index there, so we can remove it, bounce, and move along (instead of rebuilding the entire index on the sending node).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org