Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Date: Wed, 24 Dec 2014 19:49:13 +0000 (UTC)
From: "Andrew Purtell (JIRA)" <jira@apache.org>
To: dev@hbase.apache.org
Message-ID: <JIRA.12493041.1292227238000.99160.1419450553819@Atlassian.JIRA>
In-Reply-To: <JIRA.12493041.1292227238000@Atlassian.JIRA>
References: <JIRA.12493041.1292227238000@Atlassian.JIRA>
 <JIRA.12493041.1292227238400@arcas>
Subject: [jira] [Resolved] (HBASE-3336) Make GC pauses more obvious to users
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HBASE-3336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Purtell resolved HBASE-3336.
-----------------------------------
    Resolution: Implemented

Recent versions of HBase have a sleeper that will warn if it misses scheduled wakeup substantially, and will print GC collection times by collector.

> Make GC pauses more obvious to users
> ------------------------------------
>
>                 Key: HBASE-3336
>                 URL: https://issues.apache.org/jira/browse/HBASE-3336
>             Project: HBase
>          Issue Type: Improvement
>          Components: regionserver
>    Affects Versions: 0.92.0
>            Reporter: Todd Lipcon
>
> We often see users hit GC pauses, but it's not obvious to them what happened. I propose we add a "GCMonitor" thread which wakes up every few seconds and checks (a) that it slept for around the right amount of time, and (b) uses the JVM GC metrics to see if there was a long pause. If a long pause is detected we should output a very loud and obnoxious message to the logs indicating that a length GC pause occurred, and point to a wiki page on the topic.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)