[
https://issues.apache.org/jira/browse/TEZ-3009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15064899#comment-15064899
]
Siddharth Seth commented on TEZ-3009:
-------------------------------------
Misinterpreted this. An error from TezTaskRuner.run() is also not always logged
- except for the logging which may happen insider of TezTaskRunner itself.
That, from looking at some logs in the past, does not always log errors.
TezTaskRunner2 in master takes care of this better - but TezChild itself does
not.
The patch for the fetchWork failing looks good. Log at ERROR level instead ? +1
other than that.
Can't comment on the UI aspects of the navigation - I would've thought that if
a task is linked to the container, the task logs would point to the container
log.
> Errors that occur during container task acquisition are not logged
> ------------------------------------------------------------------
>
> Key: TEZ-3009
> URL: https://issues.apache.org/jira/browse/TEZ-3009
> Project: Apache Tez
> Issue Type: Bug
> Affects Versions: 0.7.0
> Reporter: Jason Lowe
> Assignee: Jason Lowe
> Attachments: TEZ-3009.001.patch
>
>
> If TezChild encounters an error while trying to obtain a task the error will
> be silently handled. This results in a mysterious shutdown of containers
> with no cause.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
