[
https://issues.apache.org/jira/browse/HDFS-9655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15109637#comment-15109637
]
Hudson commented on HDFS-9655:
------------------------------
FAILURE: Integrated in Hadoop-trunk-Commit #9142 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/9142/])
HDFS-9655. NN should start JVM pause monitor before loading fsimage. (lei: rev
2ec438e8f7cd77cb48fd1264781e60a48e331908)
*
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/NameNode.java
*
hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/util/JvmPauseMonitor.java
* hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
> NN should start JVM pause monitor before loading fsimage
> --------------------------------------------------------
>
> Key: HDFS-9655
> URL: https://issues.apache.org/jira/browse/HDFS-9655
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: John Zhuge
> Assignee: John Zhuge
> Priority: Critical
> Attachments: HDFS-9655.001.patch
>
>
> We have seen many cases of NameNode startup either extremely slow or even
> hung. Most of them were caused by insufficient heap size with regard to the
> metadata size. Those cases were resolved by increasing the heap size.
> However it did take support team some time to root cause. JVM pause warning
> messages would greatly assist in such diagnosis, but NN starts JVM pause
> monitor after fsimage/edits loading.
> Propose to start JVM pause monitor before loading fsimage/edits.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
