[
https://issues.apache.org/jira/browse/MAPREDUCE-3862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13211209#comment-13211209
]
Vinod Kumar Vavilapalli commented on MAPREDUCE-3862:
----------------------------------------------------
bq. we have to be able to handle starting up from an unclean shutdown, so files
need to be deleted on startup as well. +1
Yes, that is what happens in 1.0.* too. You know of an open ticket for this?
> Nodemanager can appear to hang on shutdown due to lingering DeletionService
> threads
> -----------------------------------------------------------------------------------
>
> Key: MAPREDUCE-3862
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3862
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2, nodemanager
> Affects Versions: 0.23.1
> Reporter: Jason Lowe
> Assignee: Jason Lowe
> Fix For: 0.23.2
>
> Attachments: MAPREDUCE-3862.patch, MAPREDUCE-3862.patch
>
>
> When a nodemanager attempts to shutdown cleanly, it's possible for it to
> appear to hang due to lingering DeletionService threads. This can occur when
> yarn.nodemanager.delete.debug-delay-sec is set to a relatively large value
> and one or more containers executes on the node shortly before the shutdown.
> The DeletionService is never calling
> {{setExecuteExistingDelayedTasksAfterShutdownPolicy()}} on the
> ScheduledThreadPoolExecutor, and it defaults to waiting for all scheduled
> tasks to complete before exiting.
--
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
