[jira] [Updated] (CASSANDRA-21469) Fix negative memtable allocator ownership when an update is shadowed by an existing row deletion when a row has a clustering key

["Stefan Miklosovic (Jira)" <ji...@apache.org>]

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

Stefan Miklosovic updated CASSANDRA-21469:
------------------------------------------
    Description: 
This ticket forks CASSANDRA-21390 where we identified a valid bug when a row contains a clustering key : suggested by Stefan Miklosovic : override of clustering row with out of order timestamp, the updated row is incorrectly accounted into heap usage while it is not actually stored (similar to CASSANDRA-18125), MR: 
https://github.com/apache/cassandra/pull/4886/changes

> Fix negative memtable allocator ownership when an update is shadowed by an existing row deletion when a row has a clustering key
> --------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-21469
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-21469
>             Project: Apache Cassandra
>          Issue Type: Bug
>          Components: Local/Memtable
>            Reporter: Stefan Miklosovic
>            Priority: Normal
>
> This ticket forks CASSANDRA-21390 where we identified a valid bug when a row contains a clustering key : suggested by Stefan Miklosovic : override of clustering row with out of order timestamp, the updated row is incorrectly accounted into heap usage while it is not actually stored (similar to CASSANDRA-18125), MR: 
> https://github.com/apache/cassandra/pull/4886/changes



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