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 2026/07/15 05:18:00 UTC

[jira] [Created] (CASSANDRA-21520) Investigate Safety of SAI Index Rebuilds and ZCS

Caleb Rackliffe created CASSANDRA-21520:
-------------------------------------------

             Summary: Investigate Safety of SAI Index Rebuilds and ZCS
                 Key: CASSANDRA-21520
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-21520
             Project: Apache Cassandra
          Issue Type: Bug
          Components: Consistency/Streaming, Feature/SAI
            Reporter: Caleb Rackliffe
            Assignee: Caleb Rackliffe


When zero-copy streaming and SAI index rebuilds overlap with one another, there are some potentially problematic interactions.

1.) What happens when we try to stream an entire SSTable, create a manifest, but then the relevant SAI components are deleted before the stream writer creates a channel for the outgoing file?

2.) What happens in the above case, if a rebuild deletes an old component, then begins writing a new one after the streaming manifest has been created?

3.) To what extent do existing mechanisms, like the assertions in ComponentContext, fail streaming operations right now rather than propagate corruption?

4.) When corrupted index components exist on disk, should streaming operations block index rebuilds? Should index rebuilds block streaming? Should active index builds degrade streaming to avoid ZCS and build indexes on the receiver?

5.) Should we verify checksums on SAI index components on the sender, rather than just the receiver as we do now?



--
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