Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
-
Reviewed
Description
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.
Attachments
Attachments
Issue Links
- causes
-
HADOOP-15679 ShutdownHookManager shutdown time needs to be configurable & extended
- Resolved
- is related to
-
HADOOP-12993 Change ShutdownHookManger complete shutdown log from INFO to DEBUG
- Resolved
-
SPARK-25183 Spark HiveServer2 registers shutdown hook with JVM, not ShutdownHookManager; race conditions can arise
- Resolved
-
HADOOP-8325 Add a ShutdownHookManager to be used by different components instead of the JVM shutdownhook
- Closed
-
HADOOP-4829 Allow FileSystem shutdown hook to be disabled
- Closed
- relates to
-
HADOOP-10219 ipc.Client.setupIOstreams() needs to check for ClientCache.stopClient requested shutdowns
- Resolved