[ https://issues.apache.org/jira/browse/IMPALA-6857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
bharath v resolved IMPALA-6857. ------------------------------- Resolution: Fixed Fix Version/s: Impala 3.1.0 Ended up doing the /jmx endpoint that is compatible with the hadoop stack. https://gerrit.cloudera.org/#/c/10998/ > Add JVM Pause Monitor to Impala Processes > ----------------------------------------- > > Key: IMPALA-6857 > URL: https://issues.apache.org/jira/browse/IMPALA-6857 > Project: IMPALA > Issue Type: Improvement > Components: Catalog, Frontend > Reporter: Philip Zeyliger > Priority: Major > Labels: ramp-up, supportability > Fix For: Impala 3.1.0 > > > 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"? -- This message was sent by Atlassian JIRA (v7.6.3#76005)