Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 24 May 2016 05:55:13 +0000 (UTC)
From: "Marcus Eriksson (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12966288.1462822315000.274109.1464069313071@Atlassian.JIRA>
In-Reply-To: <JIRA.12966288.1462822315000@Atlassian.JIRA>
References: <JIRA.12966288.1462822315000@Atlassian.JIRA> <JIRA.12966288.1462822315310@arcas>
Subject: [jira] [Updated] (CASSANDRA-11739) Cache key references might cause
 OOM on incremental repair
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 24 May 2016 05:55:14 -0000


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

Marcus Eriksson updated CASSANDRA-11739:
----------------------------------------
       Resolution: Fixed
    Fix Version/s: 3.0.7
                   3.7
                   2.2.7
                   2.1.15
           Status: Resolved  (was: Patch Available)

committed!

> 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
>             Fix For: 2.1.15, 2.2.7, 3.7, 3.0.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)