[
https://issues.apache.org/jira/browse/TEZ-2216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14372415#comment-14372415
]
Jeff Zhang edited comment on TEZ-2216 at 3/21/15 1:20 AM:
----------------------------------------------------------
This could be done to some certain extent. Depends on 2 things:
* whether DAGClientServer is started ( Client get diagnostics from
DAGClientServer
* whether YarnTaskSchedulerService is started ( YarnTaskScheduler will
unregister it from RM, and push diagnostics to RM, Client get diagnostics from
RM ). For the error on AM initialization, maybe YarnTaskSchedulerService is the
key.
was (Author: zjffdu):
This could be done to some certain extent. Depends on 2 things:
* whether DAGClientServer is started ( Client get diagnostics from
DAGClientServer
* whether YarnTaskSchedulerService is started ( YarnTaskScheduler will
unregister it from RM, and push diagnostics to RM, Client get diagnostics from
RM )
> Expose errors during AM initialization
> --------------------------------------
>
> Key: TEZ-2216
> URL: https://issues.apache.org/jira/browse/TEZ-2216
> Project: Apache Tez
> Issue Type: Bug
> Reporter: Bikas Saha
>
> If there are bad configs or other issues that cause errors/exceptions during
> AM initialization (eg. during service init) then those errors are not exposed
> to the user. Exposing them would be useful in quickly debugging such issues.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
