[ https://issues.apache.org/jira/browse/TEZ-3368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15553501#comment-15553501 ]
TezQA commented on TEZ-3368: ---------------------------- {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12819210/TEZ-3368.001.patch against master revision 149db1b. {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:red}-1 tests included{color}. The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:green}+1 javadoc{color}. There were no new javadoc warning messages. {color:green}+1 findbugs{color}. The patch does not introduce any new Findbugs (version ) warnings. {color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings. {color:red}-1 core tests{color}. The test build failed in Test results: https://builds.apache.org/job/PreCommit-TEZ-Build/2023//testReport/ Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/2023//console This message is automatically generated. > NPE in DelayedContainerManager > ------------------------------ > > Key: TEZ-3368 > URL: https://issues.apache.org/jira/browse/TEZ-3368 > Project: Apache Tez > Issue Type: Bug > Affects Versions: 0.7.1 > Reporter: Jason Lowe > Assignee: Jason Lowe > Attachments: TEZ-3368.001.patch > > > Saw a Tez AM hang due to an NPE in the DelayedContainerManager: > {noformat} > 2016-07-17 01:53:23,157 [ERROR] [DelayedContainerManager] > |yarn.YarnUncaughtExceptionHandler|: Thread > Thread[DelayedContainerManager,5,main] threw an Exception. > java.lang.NullPointerException > at > org.apache.tez.dag.app.rm.TezAMRMClientAsync.getMatchingRequestsForTopPriority(TezAMRMClientAsync.java:142) > at > org.apache.tez.dag.app.rm.YarnTaskSchedulerService.getMatchingRequestWithoutPriority(YarnTaskSchedulerService.java:1474) > at > org.apache.tez.dag.app.rm.YarnTaskSchedulerService.access$500(YarnTaskSchedulerService.java:84) > at > org.apache.tez.dag.app.rm.YarnTaskSchedulerService$NodeLocalContainerAssigner.assignReUsedContainer(YarnTaskSchedulerService.java:1869) > at > org.apache.tez.dag.app.rm.YarnTaskSchedulerService.assignReUsedContainerWithLocation(YarnTaskSchedulerService.java:1753) > at > org.apache.tez.dag.app.rm.YarnTaskSchedulerService.assignDelayedContainer(YarnTaskSchedulerService.java:733) > at > org.apache.tez.dag.app.rm.YarnTaskSchedulerService.access$600(YarnTaskSchedulerService.java:84) > at > org.apache.tez.dag.app.rm.YarnTaskSchedulerService$DelayedContainerManager.run(YarnTaskSchedulerService.java:2030) > {noformat} > After the DelayedContainerManager thread exited the AM proceeded to receive > requested containers that would go unused until the container allocations > expired. Then they would be re-requested, and the cycle repeated > indefinitely. -- This message was sent by Atlassian JIRA (v6.3.4#6332)