[
https://issues.apache.org/jira/browse/TEZ-3335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15556104#comment-15556104
]
TezQA commented on TEZ-3335:
----------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12818224/TEZ-3335.001.patch
against master revision dceb365.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{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:red}-1 findbugs{color}. The patch appears to introduce 1 new
Findbugs (version 3.0.1) 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 following test timeouts occurred in :
org.apache.tez.mapreduce.TestMRRJobsDAGApi
Test results:
https://builds.apache.org/job/PreCommit-TEZ-Build/2024//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-TEZ-Build/2024//artifact/patchprocess/newPatchFindbugsWarningstez-dag.html
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/2024//console
This message is automatically generated.
> DAG client thinks app is still running when app status is null
> --------------------------------------------------------------
>
> Key: TEZ-3335
> URL: https://issues.apache.org/jira/browse/TEZ-3335
> Project: Apache Tez
> Issue Type: Bug
> Affects Versions: 0.7.1
> Reporter: Jason Lowe
> Assignee: Jason Lowe
> Attachments: TEZ-3335.001.patch
>
>
> When an RM restarts without recovering apps (i.e.: either work-preserving is
> not enabled or state store was removed) and the YARN application history is
> enabled then YarnClient can return an application report with the app status
> as null. The RM doesn't know about the application, so the client redirects
> to the AHS. The AHS knows the app started at some point but will never
> received a finished event, hence the null app status.
> The DAG client fails to detect this scenario and believes the app is still
> running, so for example Hive clients will continue to hammer for status on an
> app that doesn't exist.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
