[ 
https://issues.apache.org/jira/browse/TEZ-3346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kuhu Shukla updated TEZ-3346:
-----------------------------
    Attachment: VertexPage.png
                DagPage_AMDiagnostics.png

> Vertex status on DAG UI and Vertex UI can be inconsistent
> ---------------------------------------------------------
>
>                 Key: TEZ-3346
>                 URL: https://issues.apache.org/jira/browse/TEZ-3346
>             Project: Apache Tez
>          Issue Type: Bug
>          Components: UI
>            Reporter: Kuhu Shukla
>         Attachments: DagPage_AMDiagnostics.png, VertexPage.png
>
>
> If the AM fails on all its attempts, the Vertex status on the DAG page is 
> "KILLED" . On clicking the vertexName, the vertex UI page shows the status as 
> "FAILED" (which it pulls from the proxy).
> I think this code in {{vertex_tasks_controller.js}} makes the decision to 
> mark the vertex as KILLED, since the Timeline Server has "RUNNING" as the 
> last updated vertex status since the AM crashed.
> {code}
>  if (taskStatus == 'RUNNING' && isUnsuccessfulVertex) {
>         taskStatus = 'KILLED'
>       }
>       if (taskStatus != task.get('status')) {
>         task.set('status', taskStatus);
>       }
>     });
> {code}
> Not sure which of the 2 values is semantically correct. The FAILED state 
> seems to come from this logic which uses appState and finalState of the 
> application from Timeline's and AHS's perspective to decide the vertex state.
> {code}
> vertex.set('status', App.Helpers.misc.getRealStatus(vertex.get('status'), 
> appDetail.get('status'),
>         appDetail.get('finalStatus')));
> {code}



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

Reply via email to