You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tez.apache.org by "Jeff Zhang (JIRA)" <ji...@apache.org> on 2015/02/13 03:51:11 UTC

[jira] [Updated] (TEZ-2086) TEZ-UI Support Task/TaskAttempt level log

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

Jeff Zhang updated TEZ-2086:
----------------------------
    Description: 
Currently on the tez-ui, there's log link for task & task attempt. But actually it points to the container log. This means if container reuse is enabled. You will see logs of attempt 1,2,3 if you click the log link of attempt 1.

And for the log link task, it only point to the container log of the successful attempt. You can't see the full log of all its attempts

This issue may due to the limitation of yarn because currently we use the yarn application history ui.


  was:
Currently on the tez-ui, there's log link for task & task attempt. But actually it points to the container log. This mean if container reuse is enabled. You will see logs of attempt 1,2,3 if you link the log link of attempt 1.

And for the task attempt, it only point the container of the successful attempt. You can't see the full log of all its attempts

This issue may due to the limitation of yarn. 



> TEZ-UI  Support Task/TaskAttempt level log
> ------------------------------------------
>
>                 Key: TEZ-2086
>                 URL: https://issues.apache.org/jira/browse/TEZ-2086
>             Project: Apache Tez
>          Issue Type: Bug
>          Components: UI
>            Reporter: Jeff Zhang
>
> Currently on the tez-ui, there's log link for task & task attempt. But actually it points to the container log. This means if container reuse is enabled. You will see logs of attempt 1,2,3 if you click the log link of attempt 1.
> And for the log link task, it only point to the container log of the successful attempt. You can't see the full log of all its attempts
> This issue may due to the limitation of yarn because currently we use the yarn application history ui.



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