hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jian He (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3131) YarnClientImpl should check FAILED and KILLED state in submitApplication
Date Mon, 23 Feb 2015 23:13:12 GMT

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

Jian He commented on YARN-3131:
-------------------------------

looks good overall, some minor comments on my side
- the enum sets are exceeding 80 column limit
- Instead of throwing IOException, we may throw YarnException.

> 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
>
>
> 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)

Mime
View raw message