You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Andrii Tkach (JIRA)" <ji...@apache.org> on 2017/09/15 11:44:00 UTC
[jira] [Comment Edited] (AMBARI-21965) Tez UI: DAG - All Task
Attempts displays no records available
[ https://issues.apache.org/jira/browse/AMBARI-21965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16167746#comment-16167746 ]
Andrii Tkach edited comment on AMBARI-21965 at 9/15/17 11:43 AM:
-----------------------------------------------------------------
trunk:
21329 passing (27s)
128 pending
branch-2.6:
30491 passing (32s)
157 pending
was (Author: atkach):
trunk:
21329 passing (27s)
128 pending
> Tez UI: DAG - All Task Attempts displays no records available
> -------------------------------------------------------------
>
> Key: AMBARI-21965
> URL: https://issues.apache.org/jira/browse/AMBARI-21965
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.5.2
> Reporter: Andrii Tkach
> Assignee: Andrii Tkach
> Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21965.patch, Screen Shot 2017-08-30 at 3.32.52 PM.png, Tez_UI.png
>
>
> On IOP->HDP upgraded clusters, "testMainUIAndAttemptUIRunningDAG" fails as Task Attempts tab in Tez View displays "no records available".
> In the test, we simply run a Tez example jar - mrrsleep, get the relevant AppID and DAG ID and look for various pages of Tez UI to reflect expected status.
> While rerunning the test, I noticed that the DAG Id(dag_1503917575003_0012_1) transitioned from INITED to RUNNING but showed no progress after and the tasks attempts page had no records.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)