You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Adam Holmberg (Jira)" <ji...@apache.org> on 2020/12/14 20:55:00 UTC
[jira] [Updated] (CASSANDRA-14834) Avoid keeping
StreamingTombstoneHistogramBuilder.Spool in memory during the whole
compaction
[ https://issues.apache.org/jira/browse/CASSANDRA-14834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Adam Holmberg updated CASSANDRA-14834:
--------------------------------------
Test and Documentation Plan:
No doc.
I didn't come with a test that would prove that we would not OOM because of this. I'm open to suggestions.
Status: Patch Available (was: In Progress)
> Avoid keeping StreamingTombstoneHistogramBuilder.Spool in memory during the whole compaction
> --------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-14834
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14834
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Compaction
> Reporter: Marcus Eriksson
> Assignee: Adam Holmberg
> Priority: Low
> Fix For: 4.0, 4.0-beta
>
>
> Since CASSANDRA-13444 {{StreamingTombstoneHistogramBuilder.Spool}} is allocated to keep around an array with 131072 * 2 * 2 integers *per written sstable* during the whole compaction. With LCS at times creating 1000s of sstables during a compaction it kills the node.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org