You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Benedict Elliott Smith (Jira)" <ji...@apache.org> on 2026/04/13 14:14:00 UTC

[jira] [Updated] (CASSANDRA-19356) Accord: Range transaction state indexing / caching

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

Benedict Elliott Smith updated CASSANDRA-19356:
-----------------------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Triage Needed)

> Accord: Range transaction state indexing / caching
> --------------------------------------------------
>
>                 Key: CASSANDRA-19356
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-19356
>             Project: Apache Cassandra
>          Issue Type: Improvement
>          Components: Accord
>            Reporter: Benedict Elliott Smith
>            Priority: Normal
>
> Range transactions are kept entirely in-memory at present. This is fine so long as we only use them for book-keeping and they do not exist too long, but runs the risk of OOM if cleanup doesn't excise them for some reason.



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