[
https://issues.apache.org/jira/browse/HADOOP-1901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12528499
]
Doug Cutting commented on HADOOP-1901:
--------------------------------------
What are the important benefits of running stopTracker() over simply having the
JVM exit? It seems to mostly just cause threads to exit and sockets to close,
which would happen anyway when the JVM exits. Is there some external state
that's changed by stopTracker()?
> JobTracker.stopTracker() is not invoked when shutting down JobTracker using
> bin/stop-{all,mapred}.sh
> ----------------------------------------------------------------------------------------------------
>
> Key: HADOOP-1901
> URL: https://issues.apache.org/jira/browse/HADOOP-1901
> Project: Hadoop
> Issue Type: Bug
> Components: mapred
> Reporter: Senthil Subramanian
> Assignee: Senthil Subramanian
> Attachments: HADOOP-1901.patch
>
>
> This can be fixed by adding a shutdown hook to the JobTracker RunTime that
> invokes stopTracker().
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
