[ https://issues.apache.org/jira/browse/HADOOP-9618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Todd Lipcon updated HADOOP-9618: -------------------------------- Status: Patch Available (was: Open) > 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 > Attachments: hadoop-9618.txt > > > 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