[
https://issues.apache.org/jira/browse/CASSANDRA-20752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18029585#comment-18029585
]
Caleb Rackliffe edited comment on CASSANDRA-20752 at 10/13/25 6:29 PM:
-----------------------------------------------------------------------
Attached another 5.0 CI run on my infra, and [same result|^ci_summary.html] .
Nothing but a couple unrelated failures.
was (Author: maedhroz):
Attached another 5.0 CI run on my infra, and same result. Nothing but a couple
unrelated failures.
> Flush SAI segment builder when current sstable writer is switched
> -----------------------------------------------------------------
>
> Key: CASSANDRA-20752
> URL: https://issues.apache.org/jira/browse/CASSANDRA-20752
> Project: Apache Cassandra
> Issue Type: Improvement
> Components: Feature/SAI
> Reporter: Zhao Yang
> Assignee: Pranav
> Priority: Normal
> Fix For: 5.0.x, 6.x
>
> Attachments: ci_summary.html
>
> Time Spent: 3h
> Remaining Estimate: 0h
>
> With sharded compaction, sstable writer may be switched when reaching
> boundary in `SSTableRewriter#switchWriter`. But the switched writer's segment
> builders are not flushed until all sharded are written and committed.
> This unccessarily retains memory causing smaller segments and may even cause
> OOM due to segment builder's min-flush-size.
> We can extend `SSTableFlushObserver` to be notified on sstable switched
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
