[
https://issues.apache.org/jira/browse/HADOOP-12950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15220810#comment-15220810
]
Hudson commented on HADOOP-12950:
---------------------------------
FAILURE: Integrated in Hadoop-trunk-Commit #9538 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/9538/])
HADOOP-12950. ShutdownHookManager should have a timeout for each of the (xyao:
rev aac4d65bf9c6d68f53610e5fe9997a391e3fa053)
*
hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/util/TestShutdownHookManager.java
*
hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/util/ShutdownHookManager.java
> ShutdownHookManager should have a timeout for each of the Registered shutdown
> hook
> ----------------------------------------------------------------------------------
>
> Key: HADOOP-12950
> URL: https://issues.apache.org/jira/browse/HADOOP-12950
> Project: Hadoop Common
> Issue Type: Improvement
> Reporter: Xiaoyu Yao
> Assignee: Xiaoyu Yao
> Fix For: 2.8.0
>
> Attachments: HADOOP-12950.00.patch, HADOOP-12950.01.patch,
> HADOOP-12950.02.patch, HADOOP-12950.03.patch, HADOOP-12950.04.patch
>
>
> HADOOP-8325 added a ShutdownHookManager to be used by different components
> instead of the JVM shutdownhook. For each of the shutdown hook registered, we
> currently don't have an upper bound for its execution time. We have seen
> namenode failed to shutdown completely (waiting for shutdown hook to finish
> after failover) for a long period of time, which breaks the namenode high
> availability scenarios. This ticket is opened to allow specifying a timeout
> value for the registered shutdown hook.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
