hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-1988) OutOfMemoryError in RegionServer
Date Thu, 19 Nov 2009 17:27:39 GMT

    [ https://issues.apache.org/jira/browse/HBASE-1988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12780151#action_12780151

stack commented on HBASE-1988:

Hey Stefan: Whats the load characteristic?  Short scans?  Many of them concurrently?  Big
cells?  Yeah, looks like hbase-1927 but must be something else.  You are closing your scanners
when done?  Please do a thread dump on the RS.  Its supposed to go down on OOME.  I'd like
to see whats keeping it up.  Also, the RS will dump its heap on OOME (by default we've that
flag set on JVM).  Any chance of your putting that dump in a public place so I can pull it
and take a look?  Thanks.

> 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.

View raw message