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

Posted to common-issues@hadoop.apache.org by "John Zhuge (JIRA)" <ji...@apache.org> on 2016/02/29 16:14:18 UTC

[jira] [Assigned] (HADOOP-12855) Add option to disable JVMPauseMonitor across services

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

John Zhuge reassigned HADOOP-12855:
-----------------------------------

    Assignee: John Zhuge

> Add option to disable JVMPauseMonitor across services
> -----------------------------------------------------
>
>                 Key: HADOOP-12855
>                 URL: https://issues.apache.org/jira/browse/HADOOP-12855
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: performance
>    Affects Versions: 2.8.0
>         Environment: JVMs with miniHDFS and miniYarn clusters
>            Reporter: Steve Loughran
>            Assignee: John Zhuge
>
> 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)