[
https://issues.apache.org/jira/browse/TEZ-900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14304194#comment-14304194
]
Hitesh Shah commented on TEZ-900:
---------------------------------
Actually, YarnClientImpl already does the former check i.e wait for it to move
out of NEW/NEW_SAVING state. However, the question is what is the guarantee
that the getAppMasterStatus will tell you whether it was accepted properly or
not?
Your patch seems to be along the same lines as YARNRunner in the MR jobclient
but it does not handle the failure case correctly i.e. checking if the app
master status is a non-failure state and throwing an exception if it did fail.
> Confusing message for incorrect queue for some tez examples
> -----------------------------------------------------------
>
> Key: TEZ-900
> URL: https://issues.apache.org/jira/browse/TEZ-900
> Project: Apache Tez
> Issue Type: Bug
> Affects Versions: 0.3.0
> Reporter: Jonathan Eagles
> Assignee: Chang Li
> Attachments: tez900.patch
>
>
> The error message of at least orderedwordcount with non-existent queue is
> very difficult as compared to mrrsleep which is very intuitive.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)