[
https://issues.apache.org/jira/browse/TEZ-3542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15679720#comment-15679720
]
Sreenath Somarajapuram commented on TEZ-3542:
---------------------------------------------
Its a known behavior.
- Why are those DAGs visible: For those DAGs the status in timeline server
(ATS) is RUNNING. As the filtering happens at the timeline server side those
DAGs manage to pass through the filter.
- Why are they having KILLED/SUCCEEDED as status: Once they are loaded the UI
communicates with RM & AM and updates the status & progress to the latest value
- causing you to see KILLED, SUCCESS etc. (This is done only for RUNNING DAGs)
- The experience have been improved in the latest UI as it have a level of
filtering at the UI side. But still its not perfect. More improvements to the
behavior were planned as part of TEZ-3371.
Why should we update status based on RM & AM: In cases where the AM is killed,
the application might not get enough time to updated the status in timeline.
Those DAGs would have status as RUNNING for ever
> Tez UI Running filter shows Killed and Successful DAGs
> ------------------------------------------------------
>
> Key: TEZ-3542
> URL: https://issues.apache.org/jira/browse/TEZ-3542
> Project: Apache Tez
> Issue Type: Bug
> Components: UI
> Affects Versions: 0.8.4
> Reporter: Premal Shah
> Priority: Minor
> Attachments: screenshot-1.png
>
>
> When filtering the Tez UI to show only RUNNING DAGs, the UI still shows
> KILLED and SUCCESSFUL tasks
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
