Mailing-List: contact common-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-dev@hadoop.apache.org
Date: Tue, 4 Jun 2013 17:31:20 +0000 (UTC)
From: "Todd Lipcon (JIRA)" <jira@apache.org>
To: common-dev@hadoop.apache.org
Message-ID: <JIRA.12650939.1370366997275.65165.1370367080672@arcas>
In-Reply-To: <JIRA.12650939.1370366997275@arcas>
References: <JIRA.12650939.1370366997275@arcas>
Subject: [jira] [Created] (HADOOP-9618) Add thread which detects JVM pauses
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Todd Lipcon created HADOOP-9618:
-----------------------------------

             Summary: Add thread which detects JVM pauses
                 Key: HADOOP-9618
                 URL: https://issues.apache.org/jira/browse/HADOOP-9618
             Project: Hadoop Common
          Issue Type: New Feature
          Components: util
    Affects Versions: 3.0.0
            Reporter: Todd Lipcon
            Assignee: Todd Lipcon


Often times users struggle to understand what happened when a long JVM pause (GC or otherwise) causes things to malfunction inside a Hadoop daemon. For example, a long GC pause while logging an edit to the QJM may cause the edit to timeout, or a long GC pause may make other IPCs to the NameNode timeout. We should add a simple thread which loops on 1-second sleeps, and if the sleep ever takes significantly longer than 1 second, log a WARN. This will make GC pauses obvious in logs.

--
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