hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bibin A Chundatt (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-4777) Retrospect Non-Existent Queue check and its error handling while submitting a new application
Date Tue, 08 Mar 2016 17:02:41 GMT

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

Bibin A Chundatt commented on YARN-4777:
----------------------------------------

Jira title can we update ?

> Retrospect Non-Existent Queue check and its error handling while submitting a new application
> ---------------------------------------------------------------------------------------------
>
>                 Key: YARN-4777
>                 URL: https://issues.apache.org/jira/browse/YARN-4777
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: resourcemanager
>    Affects Versions: 2.7.2
>            Reporter: Sunil G
>            Assignee: Sunil G
>
> After YARN-4764, non-existent-queue scenarios while submission of new application will
be same for acl Or non-acl ways.
> However as per discussion there, its better to handle basic queue level validation in
RMApp itself. This saves few state transitions to RMApp and its attempt etc. Such cases can
also be audit logged so information will not be lost.
> I will share an approach soon.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message