[ https://issues.apache.org/jira/browse/MAPREDUCE-3862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13208955#comment-13208955 ]
Hadoop QA commented on MAPREDUCE-3862: -------------------------------------- +1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12514725/MAPREDUCE-3862.patch against trunk revision . +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 3 new or modified tests. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 eclipse:eclipse. The patch built with eclipse:eclipse. +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. +1 core tests. The patch passed unit tests in . +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1870//testReport/ Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1870//console This message is automatically generated. > 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 > 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