[
https://issues.apache.org/jira/browse/YARN-3131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14329012#comment-14329012
]
Jason Lowe commented on YARN-3131:
----------------------------------
Actually just saw YARN-3232 was filed which proposes to stop exposing the
NEW_SAVING and SUBMITTED states to clients. If we do that then all we need to
do in YarnClientImpl is have it throw when the non-NEW state is FAILED or
KILLED to indicate the submit failed.
> YarnClientImpl should check FAILED and KILLED state in submitApplication
> ------------------------------------------------------------------------
>
> Key: YARN-3131
> URL: https://issues.apache.org/jira/browse/YARN-3131
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Chang Li
> Assignee: Chang Li
> Attachments: yarn_3131_v1.patch
>
>
> Just run into a issue when submit a job into a non-existent queue and
> YarnClient raise no exception. Though that job indeed get submitted
> successfully and just failed immediately after, it will be better if
> YarnClient can handle the immediate fail situation like YarnRunner does
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
