You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tez.apache.org by "Hitesh Shah (JIRA)" <ji...@apache.org> on 2015/10/08 06:42:27 UTC
[jira] [Comment Edited] (TEZ-2870) Tez UI: DAG status is not
correct when application history is not accessible.
[ https://issues.apache.org/jira/browse/TEZ-2870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14948066#comment-14948066 ]
Hitesh Shah edited comment on TEZ-2870 at 10/8/15 4:42 AM:
-----------------------------------------------------------
The RM will never provide the final DAG status as it only knows about yarn apps and not Tez dags. A YARN app can run multiple DAGs. The best that YARN can provide is info that whether a DAG is completed or not based on whether the YARN app has completed or not.
was (Author: hitesh):
The RM will never provide the final DAG status. A YARN app can run multiple DAGs. The best that YARN can provide is info that whether a DAG is completed or not based on whether the YARN app has completed or not.
> Tez UI: DAG status is not correct when application history is not accessible.
> -----------------------------------------------------------------------------
>
> Key: TEZ-2870
> URL: https://issues.apache.org/jira/browse/TEZ-2870
> Project: Apache Tez
> Issue Type: Bug
> Reporter: Sreenath Somarajapuram
>
> When data is available in RM use RM API to correct the final DAG status than application history.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)