[
https://issues.apache.org/jira/browse/CASSANDRA-11739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15276886#comment-15276886
]
Paulo Motta commented on CASSANDRA-11739:
-----------------------------------------
Idea is to track only SSTable data component filename on parent repair session,
rather than {{SSTableReader}} references. When doing anti-compaction, get
references of existing sstables from CFS. WDYT [~krummas]?
> Cache key references might cause OOM on incremental repair
> ----------------------------------------------------------
>
> Key: CASSANDRA-11739
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11739
> Project: Cassandra
> Issue Type: Bug
> Reporter: Paulo Motta
> Assignee: Paulo Motta
> Attachments: heapdump.png
>
>
> We keep {{SSTableReader}} references for the duration of the repair to
> anti-compact later, and their tidier keep references to cache keys to be
> invalidated which are only cleaned up by GC after repair is finished. These
> cache keys can accumulate while repair is being executed leading to OOM for
> large tables/keyspaces.
> Heap dump attached.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
