[ 
https://issues.apache.org/jira/browse/TEZ-2761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14729175#comment-14729175
 ] 

Sreenath Somarajapuram edited comment on TEZ-2761 at 9/3/15 2:44 PM:
---------------------------------------------------------------------

Just observed two more issues:
1. If we move out of DAG details page while its running(Like come back to All 
Dags), polling is not stopped and causes console error.
- UI starts hitting RM with an invalid url -  
http://192.168.56.101:8088/proxy/undefined/ws/v2/tez/verticesInfo?dagID=&_=1441290684755
- May be if appId is undefined we can stop polling.

2. At times AM stops before the UI can get the final status & commit does not 
reach the client.
- DAG details just displays status as running and progress 100%. Also the 
polling is not stopped and causes console error.
- Final data returned by AM is 
{"dag":{"progress":"1.0","id":"dag_1441285134705_0025_1","status":"RUNNING"}}, 
may be if AM is not reachable and progress is 1, we must set progress to 
SUCCEEDED.



was (Author: sreenath):
Just observed two more issues:
1. If we move out of DAG details page while its running(Like come back to All 
Dags), polling is not stopped and causes console error.
- UI starts hitting RM with an invalid url -  
http://192.168.56.101:8088/proxy/undefined/ws/v2/tez/verticesInfo?dagID=&_=1441290684755

2. At times AM stops before the UI can get the final status & commit does not 
reach the client.
- DAG details just displays status as running and progress 100%. Also the 
polling is not stopped and causes console error.
- Final data returned by AM is 
{"dag":{"progress":"1.0","id":"dag_1441285134705_0025_1","status":"RUNNING"}}, 
may be if AM is not reachable and progress is 1, we must set progress to 
SUCCEEDED.


> Tez UI: update the progress on the various pages on the UI
> ----------------------------------------------------------
>
>                 Key: TEZ-2761
>                 URL: https://issues.apache.org/jira/browse/TEZ-2761
>             Project: Apache Tez
>          Issue Type: Sub-task
>          Components: UI
>            Reporter: Prakash Ramachandran
>            Assignee: Prakash Ramachandran
>         Attachments: TEZ-2761.1.patch, TEZ-2761.2.patch, TEZ-2761.wip.1.patch
>
>
> The data displayed on the UI for running tasks should be updated with the 
> latest status fetched from AM.
> This includes the status, progress, task count etc. The api should also allow 
> querying the values for the tasks (running, failed, succeeded...).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to