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

Posted to issues@impala.apache.org by "Philip Zeyliger (JIRA)" <ji...@apache.org> on 2018/04/16 18:11:00 UTC

[jira] [Created] (IMPALA-6857) Add JVM Pause Monitor to Impala Processes

Philip Zeyliger created IMPALA-6857:
---------------------------------------

             Summary: Add JVM Pause Monitor to Impala Processes
                 Key: IMPALA-6857
                 URL: https://issues.apache.org/jira/browse/IMPALA-6857
             Project: IMPALA
          Issue Type: Task
            Reporter: Philip Zeyliger


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)