Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 96310101CE for ; Tue, 9 Jul 2013 15:51:51 +0000 (UTC) Received: (qmail 32292 invoked by uid 500); 9 Jul 2013 15:51:51 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 32141 invoked by uid 500); 9 Jul 2013 15:51:51 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 32012 invoked by uid 99); 9 Jul 2013 15:51:50 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Jul 2013 15:51:50 +0000 Date: Tue, 9 Jul 2013 15:51:50 +0000 (UTC) From: "Andrew Purtell (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (HBASE-2039) G1 GC issues MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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