Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-dev@hadoop.apache.org
Message-ID: <252289765.1228641704701.JavaMail.jira@brutus>
Date: Sun, 7 Dec 2008 01:21:44 -0800 (PST)
From: "stack (JIRA)" <jira@apache.org>
To: hbase-dev@hadoop.apache.org
Subject: [jira] Updated: (HBASE-900) Regionserver memory leak causing OOME
 during relatively modest bulk importing
In-Reply-To: <545424030.1222300426159.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

stack updated HBASE-900:
------------------------

    Attachment: 900.patch

Patch that brings down Server and Client from hadoop ipc.  We now have bulk of hadoop ipc local.  Classes have been renamed to have an HBase prefix to distingush them from their hadoop versions.  Had to bring at least Server local because fix needed meddling in private class (Server.Handler).  Added check on size of stack-based ByteArrayOutputStream size after every use.  It used to always reset.  Now, if BAOS is > initial buffersize, we allocate a new BAOS instance rather than reset.

Verified in testbed it does the right thing.  Unit tests pass.  Tempted to commit but maybe Andrew you can give it a spin first?

Next will work on the blockcache leak.

> Regionserver memory leak causing OOME during relatively modest bulk importing
> -----------------------------------------------------------------------------
>
>                 Key: HBASE-900
>                 URL: https://issues.apache.org/jira/browse/HBASE-900
>             Project: Hadoop HBase
>          Issue Type: Bug
>    Affects Versions: 0.18.1, 0.19.0
>            Reporter: Jonathan Gray
>            Assignee: stack
>            Priority: Blocker
>         Attachments: 900.patch, memoryOn13.png
>
>
> I have recreated this issue several times and it appears to have been introduced in 0.2.
> During an import to a single table, memory usage of individual region servers grows w/o bounds and when set to the default 1GB it will eventually die with OOME.  This has happened to me as well as Daniel Ploeg on the mailing list.  In my case, I have 10 RS nodes and OOME happens w/ 1GB heap at only about 30-35 regions per RS.  In previous versions, I have imported to several hundred regions per RS with default heap size.
> I am able to get past this by increasing the max heap to 2GB.  However, the appearance of this in newer versions leads me to believe there is now some kind of memory leak happening in the region servers during import.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.