[
https://issues.apache.org/jira/browse/YARN-3131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14324980#comment-14324980
]
Hitesh Shah commented on YARN-3131:
-----------------------------------
bq. So is it important to know the AM is actually running?
Not really. I think it goes back to my original question. Should an app with
invalid configs be accepted in the first place? There is overhead in terms of
saving the app submission context etc - should some of the checks be done
before this step so as to not incur the overhead of storing the app data as
well as moving it through the app state machine?
> 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
>
> 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)
