[
https://issues.apache.org/jira/browse/TEZ-900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14304297#comment-14304297
]
Chang Li commented on TEZ-900:
------------------------------
[~hitesh] And on the Tez side, I have tested my patch and it did print out
useful information in the case of submit to the wrong queue. Though
getAppMasterStatus() doesn't handle FAILED case, but in the case of submit to
the wrong queue the job will also be at KILLED state. I can modify the
getAppMasterStatus() to make it handle the FAILED case. I think calling
getAppMasterStatus() at the end of submitDAG() can solve the problem in TEZ
side. What do you think?
> 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)
