[
https://issues.apache.org/jira/browse/TEZ-2216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389321#comment-14389321
]
Chang Li edited comment on TEZ-2216 at 3/31/15 8:21 PM:
--------------------------------------------------------
[~bikassaha], [~zjffdu], I am interested in working on this issue. I just added
a simple try catch block within serviceInit in YarnTaskSchedulerService based
on Jeff's finding. Is it sufficient? Thanks
was (Author: lichangleo):
[~bikassaha], [~zjffdu], I am interested in working on this issue. I just did a
simple try catch within serviceInit in YarnTaskSchedulerService based on Jeff's
finding. Is it sufficient? Thanks
> 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
> Attachments: TEZ-2216.1.patch
>
>
> 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)
