You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2016/02/29 15:42:18 UTC

[jira] [Created] (HADOOP-12855) improvement

Steve Loughran created HADOOP-12855:
---------------------------------------

             Summary: improvement
                 Key: HADOOP-12855
                 URL: https://issues.apache.org/jira/browse/HADOOP-12855
             Project: Hadoop Common
          Issue Type: Bug
          Components: Add option to disable JVMPauseMonitor across services
    Affects Versions: 2.8.0
         Environment: JVMs with miniHDFS and miniYarn clusters
            Reporter: Steve Loughran


Now that the YARN and HDFS services automatically start a JVM pause monitor, if you start up the mini HDFS and YARN clusters, with history server, you are spinning off 5 + threads, all looking for JVM pauses, all printing things out when it happens.

We do not need these monitors in minicluster testing; they merely add load and noise to tests.

Rather than retrofit new options everywhere, how about having a "jvm.pause.monitor.enabled" flag (default true), which, when set, starts off the monitor thread.

That way, the existing code is unchanged, there is always a JVM pause monitor for the various services —it just isn't spinning up threads.



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