[
https://issues.apache.org/jira/browse/CASSANDRA-18216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18114082#comment-18114082
]
Caleb Rackliffe edited comment on CASSANDRA-18216 at 10/5/26 8:50 PM:
----------------------------------------------------------------------
Attached CI results for the trunk branch. There are no regressions there.
(Typical mix of known simulator flakes, unterminated threads in a couple AST
tests, and unrelated upgrade test failure, etc.)
was (Author: maedhroz):
Attached [CI results for the trunk branch|^ci_summary.html]. There are no
regressions there. (Typical mix of known simulator flakes, unterminated threads
in a couple AST tests, and unrelated upgrade test failure, etc.)
> 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: 7.x
>
> Time Spent: 12h
> Remaining Estimate: 0h
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
