[
https://issues.apache.org/jira/browse/YARN-3131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14328376#comment-14328376
]
Hitesh Shah commented on YARN-3131:
-----------------------------------
[~lichangleo] I do not think that continuously polling until RUNNING is a good
idea. The most common case on a busy cluster is that an app can be submitted at
time X but not start running until a long time later. Making client code block
until then is not a good idea especially for cases where jobs are submitted in
a fire-n-forget manner.
I think for now, we should probably not address this jira in this manner. As it
stands today, it might be better to live with these issues in the short term (
so as to not break current expected behavior ).
As I mentioned earlier, I still believe that doing some basic checks in-line in
ClientRMService itself and throwing an exception back straight away is probably
a better idea than polling for any RUNNING/FAILED state.
> 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)
