[ 
https://issues.apache.org/jira/browse/CASSANDRA-21469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18089886#comment-18089886
 ] 

Stefan Miklosovic edited comment on CASSANDRA-21469 at 6/19/26 7:55 AM:
------------------------------------------------------------------------

CASSANDRA-21390 branches are meant for CASSANDRA-21469, I just did not rename 
them. Builds below:

4.0  
https://app.circleci.com/pipelines/github/instaclustr/cassandra/6501/workflows/9b666c93-89c8-4c2b-b052-a3409c9f5969
4.1 
https://app.circleci.com/pipelines/github/instaclustr/cassandra/6510/workflows/8b3c97b8-5e3f-4d88-a9fa-c0a93ad5bb24
5.0 https://pre-ci.cassandra.apache.org/job/cassandra-5.0/138/#showFailuresLink
6.0 https://pre-ci.cassandra.apache.org/job/cassandra-6.0/72/#showFailuresLink


was (Author: smiklosovic):
CASSANDRA-21390 branches are meant for CASSANDRA-21469, I just did not rename 
them. Builds below:

4.0  
https://app.circleci.com/pipelines/github/instaclustr/cassandra/6501/workflows/9b666c93-89c8-4c2b-b052-a3409c9f5969
4.1 
5.0 https://pre-ci.cassandra.apache.org/job/cassandra-5.0/138/#showFailuresLink
6.0 https://pre-ci.cassandra.apache.org/job/cassandra-6.0/72/#showFailuresLink

> 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
>            Assignee: Stefan Miklosovic
>            Priority: Normal
>             Fix For: 4.0.x, 4.1.x, 5.0.x, 6.x, 7.x
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to