You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Paulo Motta (JIRA)" <ji...@apache.org> on 2016/11/11 14:51:00 UTC

[jira] [Updated] (CASSANDRA-11739) Cache key references might cause OOM on incremental repair

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

Paulo Motta updated CASSANDRA-11739:
------------------------------------
    Component/s: Streaming and Messaging

> 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
>          Components: Streaming and Messaging
>            Reporter: Paulo Motta
>            Assignee: Paulo Motta
>              Labels: lcs, repair
>             Fix For: 2.1.15, 2.2.7, 3.0.7, 3.7
>
>         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)