[
https://issues.apache.org/jira/browse/HADOOP-12950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xiaoyu Yao updated HADOOP-12950:
--------------------------------
Resolution: Fixed
Fix Version/s: 2.8.0
Status: Resolved (was: Patch Available)
Thanks [~jingzhao] for the reviews. I've committed the patch to trunk, branch-2
and branch-2.8.
The delta from patch v04 is removing the unused import
(java.util.concurrent.ThreadFactory) as reported in the checkstyle report.
> 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)
