[
https://issues.apache.org/jira/browse/TEZ-900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14303649#comment-14303649
]
Hitesh Shah commented on TEZ-900:
---------------------------------
[~lichangleo] Understood but fighting to explain to someone how to use the API
in a "correct" way is not the right battle to fight. Also, it means that there
is a problem in the API in the first place.
Let us consider the case of submitting a yarn application to an invalid queue.
First question - does YarnClient::submitApplication throw an exception if the
app was submitted to an invalid queue? If yes, this should be bubbled up back
to the user in either TezClient::start() or TezClient::submitDAG(). If not,
this becomes a YARN bug. If the error shows up asynchronously, relying on
getAppMasterStatus is flaky as that becomes timing dependent i.e if a user
calls it too quickly, the app might not be in its final state.
In either case, let us consider the case that the user does not call
getAppMasterStatus() or waitTIllReady(). I think in this case, we should fix
the submitDAG ( and any other APIs that the user may call ) to propagate the
error back in both the session and non-session cases if the AM failed to launch
properly.
> 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
>
> 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)
