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

Vinod Kumar Vavilapalli commented on YARN-3131:
-----------------------------------------------

Nits:
{code}
+            throw new YarnException("Failed to submit " + applicationId +
+                "to YARN : " + appReport.getDiagnostics());
{code}
You will see the output to be something like "application_123456_0001to YARN" - 
a missing space

We can just simply check for failToSubmitStates? Why do we also need to check 
for waitingStates?

> 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, 
> yarn_3131_v3.patch, yarn_3131_v4.patch, yarn_3131_v5.patch, yarn_3131_v6.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