Description
Often times users struggle to understand what happened when a long JVM pause (GC or otherwise) causes things to malfunction inside a Hadoop daemon. For example, a long GC pause while logging an edit to the QJM may cause the edit to timeout, or a long GC pause may make other IPCs to the NameNode timeout. We should add a simple thread which loops on 1-second sleeps, and if the sleep ever takes significantly longer than 1 second, log a WARN. This will make GC pauses obvious in logs.
Attachments
Attachments
Issue Links
- relates to
-
HBASE-9630 Add thread which detects JVM pauses like HADOOP's
-
- Closed
-
-
MAPREDUCE-6443 Add JvmPauseMonitor to Job History Server
-
- Resolved
-
-
YARN-4019 Add JvmPauseMonitor to ResourceManager and NodeManager
-
- Resolved
-
-
YARN-4031 Add JvmPauseMonitor to ApplicationHistoryServer and WebAppProxyServer
-
- Resolved
-
-
OOZIE-1826 Add thread which detects JVM pauses
-
- Closed
-