[jira] Commented: (HBASE-2039) G1 GC issues

["stack (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HBASE-2039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12789648#action_12789648 ] 

stack commented on HBASE-2039:
------------------------------

The way we get heap size doesn't seem to work when G1 in operation:

{code}
2009-12-10 22:50:50,216 [IPC Server handler 8 on 60020] INFO org.apache.hadoop.hbase.regionserver.MemStoreFlusher: Forced flushing of TestTable,0012079792,1260483094491 because global memstore limit of 3.2m exceeded; currently 
19.1m and flushing till 2.0m
{code}

Heap in above is actually 3.4G

> G1 GC issues
> ------------
>
>                 Key: HBASE-2039
>                 URL: https://issues.apache.org/jira/browse/HBASE-2039
>             Project: Hadoop HBase
>          Issue Type: Bug
>            Reporter: stack
>
> Lets keep an issue where we report on g1 issues.  Lets keep list of crashes we see.
> I filed an issue up on bug parade.  Lets see if it becomes actual bug.  Below I note version of vm and the type of crash (Internal Error (nmethod.cpp:1981), pid=32319..... Its a 'fatal error').  It happens for me after 5-10 minutes when a loading test.  Same thing each time.
> G1 in 1.6 seems plain broke; crashes on use of stuff in concurrent utils package.
> Date Created: Thu Dec 10 13:33:04 MST 2009
> ..
> Synopsis:    Running G1 GC, crashes with " Internal Error (nmethod.cpp:1981), pid=32319..."
> Description:
>  FULL PRODUCT VERSION :
> java version "1.7.0-ea"
> Java(TM) SE Runtime Environment (build 1.7.0-ea-b77)
> Java HotSpot(TM) 64-Bit Server VM (build 17.0-b05, mixed mode)
> FULL OS VERSION :
> Fedora Core release 6 (Zod)
> EXTRA RELEVANT SYSTEM CONFIGURATION :
> Here are the JVM args:
> -XX:+HeapDumpOnOutOfMemoryError -XX:+UnlockExperimentalVMOptions -XX:+UseG1GC

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