Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 7 Oct 2014 07:39:33 +0000 (UTC)
From: "Benoit Lacelle (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12746341.1412667557000.206259.1412667573888@Atlassian.JIRA>
In-Reply-To: <JIRA.12746341.1412667557000@Atlassian.JIRA>
References: <JIRA.12746341.1412667557000@Atlassian.JIRA>
 <JIRA.12746341.1412667557926@arcas>
Subject: [jira] [Created] (CASSANDRA-8066) High Heap Consumption due to high
 number of SSTableReader
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Benoit Lacelle created CASSANDRA-8066:
-----------------------------------------

             Summary: High Heap Consumption due to high number of SSTableReader
                 Key: CASSANDRA-8066
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8066
             Project: Cassandra
          Issue Type: Bug
          Components: Core
         Environment: Cassandra 2.1.0
            Reporter: Benoit Lacelle


Given a workload with quite a lot of reads, I recently encountered high heap memory consumption. Given 2GB of Heap, it appears I have 750.000+ tasks in SSTableReader.syncExecutor, consuming more than 1.2GB. These tasks have type SSTableReader$5, which I guess corresponds to :

{code}
readMeterSyncFuture = syncExecutor.scheduleAtFixedRate(new Runnable()
{
public void run()
{
if (!isCompacted.get())
{
meterSyncThrottle.acquire();
SystemKeyspace.persistSSTableReadMeter(desc.ksname, desc.cfname, desc.generation, readMeter);
}
}
}, 1, 5, TimeUnit.MINUTES);
{code}

I do not have have to the environment right now, but I could provide a threaddump later if necessary.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)