[ 
https://issues.apache.org/jira/browse/YARN-3131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14329380#comment-14329380
 ] 

Chang Li commented on YARN-3131:
--------------------------------

Updated patch, fixed unit test and improved the code style. Thanks both 
[~jlowe] and [~hitesh] for providing valuable opinions. 
[~hitesh]We could open new jira(s) to address the issue of confirming AM gets 
launched. The current fix could be a short term solution because transition 
from submit state to accept state won't take too long as explained by Jason. We 
are not polling for Running/Failed state. It's not optimized but the situations 
of submitting work to a incorrect queue aren't common either.
[~zjshen][~jianhe]Could you please kindly also comment on this problem? Thanks. 

> 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, yarn_3131_v2.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)

Reply via email to