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/06/22 18:23:00 UTC

[jira] [Updated] (CASSANDRA-18216) Allow sharding of the SAI in-memory index

     [ https://issues.apache.org/jira/browse/CASSANDRA-18216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Caleb Rackliffe updated CASSANDRA-18216:
----------------------------------------
    Test and Documentation Plan: see [https://github.com/apache/cassandra/pull/4885] (includes JMH tests)
                         Status: Patch Available  (was: In Progress)

> Allow sharding of the SAI in-memory index 
> ------------------------------------------
>
>                 Key: CASSANDRA-18216
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-18216
>             Project: Apache Cassandra
>          Issue Type: Improvement
>          Components: Feature/SAI
>            Reporter: Mike Adamson
>            Assignee: Yash Sunil Nasery
>            Priority: Normal
>              Labels: SAI
>             Fix For: 6.x
>
>
> The Memtable implementation allows it to be split into a number of shards. This reduces contention during writes. 
> The MemtableIndex in SAI should follow this practice. It currently does not support sharding so all writes hit the same synchronized write block. The in-memory index search can also use the sharding to reduce the number of indexes that it searches based on the key range passed to the search.
> This exists already in the DS fork: https://github.com/datastax/cassandra/pull/298



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