[ https://issues.apache.org/jira/browse/HBASE-2039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Purtell resolved HBASE-2039. ----------------------------------- Resolution: Cannot Reproduce 7u4 was the release where G1 is officially marked as stable. Sematext is running with G1 enabled: http://blog.sematext.com/2013/06/24/g1-cms-java-garbage-collector. I've been running cluster tests with G1 and haven't observed issues. Resolving as 'Cannot Reproduce'. Reopen if G1 crashes are observed post 7u4. > G1 GC issues > ------------ > > Key: HBASE-2039 > URL: https://issues.apache.org/jira/browse/HBASE-2039 > Project: HBase > Issue Type: Sub-task > 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. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira