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:33:27 UTC
[jira] [Commented] (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=14948061#comment-14948061 ]
Hitesh Shah commented on TEZ-2870:
----------------------------------
This is an edge case when the application crashes with the AM not fulling pushing info to Timeline.
Some points to note:
- to check if the DAG has completed ( when timeline does not have a final dag status), check RM to see if yarn application has completed.
- If the RM does not have data in its memory, it will try and get the data from application history if system metrics publisher is enabled
- One thing that is guaranteed is that if the RM does not have it in its memory, this means that the app has completed ( final status unknown )
> 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)