[IMPALA-6857] Add JVM Pause Monitor to Impala Processes

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: Impala 3.1.0
• Component/s: Catalog, Frontend
• Labels: ramp-up supportability
• Epic Link: SupportabilityRoadMap
• Epic Color: ghx-label-7
• Assignee: Unassigned
• Reporter: Philip Martin
• Created: 16/Apr/18 18:10
• Updated: 27/Sep/18 20:43
• Resolved: 09/Aug/18 06:29

Description

In IMPALA-3114, we added a pause monitor for Impala. In addition to that, we should port/borrow Hadoop's JvmPauseMonitor https://github.com/apache/hadoop/blob/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/util/JvmPauseMonitor.java. I believe that when the JVM is aggressively GCing, the C++ threads will continue to get scheduled (and won't log), but the Java ones will log. (I've definitely seen JvmPauseMonitor be accurate many times.)

bharathv, when you were testing this, were you able to reproduce it triggering when the JVM half was in "GC hell"?

Issue Links

• relates to: IMPALA-7416 Expose pause monitor metrics