You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Bibin A Chundatt (JIRA)" <ji...@apache.org> on 2016/03/08 18:00:42 UTC
[jira] [Commented] (YARN-4777) Retrospect Non-Existent Queue check
and its error handling while submitting a new application
[ https://issues.apache.org/jira/browse/YARN-4777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15185237#comment-15185237 ]
Bibin A Chundatt commented on YARN-4777:
----------------------------------------
[~sunilg]
IIUC this jira is not only for non-existent queue validation its for pushing the validations like ( parent queue, invalid queue etc ) from scheduler to createAppManager rt??
> 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)