You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2012/12/04 07:52:00 UTC
[jira] [Resolved] (HBASE-1648) heap usage and limit reporting
doesn't work as expected when using G1 GC
[ https://issues.apache.org/jira/browse/HBASE-1648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack resolved HBASE-1648.
--------------------------
Resolution: Invalid
Assignee: liang xie
Closing as not valid -- problem in JVM. Assigning [~xieliang007] since the man did the work to figure it.
> heap usage and limit reporting doesn't work as expected when using G1 GC
> ------------------------------------------------------------------------
>
> Key: HBASE-1648
> URL: https://issues.apache.org/jira/browse/HBASE-1648
> Project: HBase
> Issue Type: Bug
> Environment: Linux Centos x86_64 5.3, Sun JDK 1.6.0_14 (HotSpot 64-Bit Server VM build 14.0-b16)
> Reporter: Andrew Purtell
> Assignee: liang xie
> Priority: Minor
>
> Getting some early experience with the G1 GC.
> Running with -Xmx1000m and HBASE_OPTS set to "-XX:+UnlockExperimentalVMOpts -XX:+UseG1GC". Regionserver heap use reports are not of much use:
> {noformat}
> hbase(main):001:0> status 'simple'
> 3 live servers
> test3:60020 1247389283042
> requests=0, regions=1, usedHeap=0, maxHeap=41
> test2:60020 1247389219994
> requests=0, regions=1, usedHeap=0, maxHeap=41
> test4:60020 1247389324563
> requests=0, regions=2, usedHeap=0, maxHeap=41
> 0 dead servers
> {noformat}
> top is about right:
> {noformat}
> PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
> 23988 hadoop 24 0 1492m 98m 10m S 0.0 2.5 0:02.65 java
> {noformat}
> Incidentally, don't try -XX:+UseG1GC and -XX:+DoEscapeAnalysis together or the JVM will rapidly segfault.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira