[
https://issues.apache.org/jira/browse/HADOOP-8325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13263864#comment-13263864
]
Alejandro Abdelnur commented on HADOOP-8325:
--------------------------------------------
I can think of 2 options:
1* Add a method in the FileSystem to disable its shutdown hook. MRAppMaster
would disable it and call closeAll() explicitly (it already does).
2* Remove the FileSystem shutdown hook completely. For process that don't call
closeAll() the NN eventually will close down the orphan sockets.
> remove FileSystem JVM shutdown hook that does closeAll()
> --------------------------------------------------------
>
> Key: HADOOP-8325
> URL: https://issues.apache.org/jira/browse/HADOOP-8325
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs
> Affects Versions: 2.0.0
> Reporter: Alejandro Abdelnur
> Assignee: Alejandro Abdelnur
> Priority: Critical
> Fix For: 2.0.0
>
>
> FileSystem adds a JVM shutdown hook when a filesystem instance is cached.
> MRAppMaster also uses a JVM shutdown hook, among other things, the
> MRAppMaster JVM shutdown hook is used to ensure state are written to HDFS.
> This creates a race condition because each JVM shutdown hook is a separate
> thread and if there are multiple JVM shutdown hooks there is not assurance of
> order of execution, they could even run in parallel.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
