[
https://issues.apache.org/jira/browse/MAPREDUCE-3862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210675#comment-13210675
]
Hudson commented on MAPREDUCE-3862:
-----------------------------------
Integrated in Hadoop-Mapreduce-0.23-Commit #571 (See
[https://builds.apache.org/job/Hadoop-Mapreduce-0.23-Commit/571/])
svn merge -c 1245781 from trunk to branch 0.23 FIXES MAPREDUCE-3862.
Nodemanager can appear to hang on shutdown due to lingering DeletionService
threads (Jason Lowe via bobby) (Revision 1245794)
Result = ABORTED
bobby : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1245794
Files :
* /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/CHANGES.txt
*
/hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/DeletionService.java
*
/hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/test/java/org/apache/hadoop/yarn/server/nodemanager/TestDeletionService.java
> 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
