Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-dev@hadoop.apache.org
Message-ID: <948813637.1259096619724.JavaMail.jira@brutus>
Date: Tue, 24 Nov 2009 21:03:39 +0000 (UTC)
From: "stack (JIRA)" <jira@apache.org>
To: hbase-dev@hadoop.apache.org
Subject: [jira] Commented: (HBASE-1988) OutOfMemoryError in RegionServer
In-Reply-To: <949676261.1258570239590.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-1988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12782162#action_12782162 ] 

stack commented on HBASE-1988:
------------------------------

Stefan has provided me with a heap dump.  About 17 byte arrays are > 146M each consuming 2.4G.  Stefan is check into it.

> OutOfMemoryError in RegionServer
> --------------------------------
>
>                 Key: HBASE-1988
>                 URL: https://issues.apache.org/jira/browse/HBASE-1988
>             Project: Hadoop HBase
>          Issue Type: Bug
>          Components: regionserver
>    Affects Versions: 0.20.2
>         Environment: Java 1.6.0_16 64bit on CentOS with 3000M max heap
>            Reporter: Stefan Will
>         Attachments: regionserver.log.gz
>
>
> RegionServers tend to die with an OutOfMemoryError under load. I expected this problem to go away with the fix for HBASE-1927 in 0.20.2 RC1, but it's still happening. Also, when this happens the cluster becomes unresponsive, even once the load on the machines has gone back down. Interestingly there are lots and lots of scanner lease expired messages right before the OOM.

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