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

Posted to common-issues@hadoop.apache.org by "Xiaoyu Yao (JIRA)" <ji...@apache.org> on 2016/03/22 21:41:25 UTC

[jira] [Updated] (HADOOP-12950) ShutdownHookManager should have a timeout for each of the Registered shutdown hook

     [ https://issues.apache.org/jira/browse/HADOOP-12950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Xiaoyu Yao updated HADOOP-12950:
--------------------------------
    Status: Patch Available  (was: Open)

> 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
>         Attachments: HADOOP-12950.00.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)