[
https://issues.apache.org/jira/browse/CASSANDRA-21469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Miklosovic updated CASSANDRA-21469:
------------------------------------------
Fix Version/s: 4.0.21
4.1.12
5.0.9
6.0-alpha2
7.0
(was: 4.0.x)
(was: 4.1.x)
(was: 5.0.x)
(was: 6.x)
(was: 7.x)
Since Version: 4.0.0
Source Control Link:
https://github.com/apache/cassandra/commit/d30ac083b8118f2f80acbebf371fc584f7d7253d
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
> 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.21, 4.1.12, 5.0.9, 6.0-alpha2, 7.0
>
>
> 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]
