[HADOOP-12855] Add option to disable JVMPauseMonitor across services

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 2.8.0
• Component/s: performance, test

Environment

JVMs with miniHDFS and miniYarn clusters

• Assignee: John Zhuge
• Reporter: Steve Loughran
• Created: 29/Feb/16 14:41
• Updated: 10/Jan/17 01:40
• Resolved: 10/Jan/17 01:40

Description

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.

Issue Links

• is related to: HADOOP-12908 Make JvmPauseMonitor a singleton
• is related to: HADOOP-12946 Ensure one JVMPauseMonitor thread per JVM
• relates to: HADOOP-12946 Ensure one JVMPauseMonitor thread per JVM