[
https://issues.apache.org/jira/browse/YARN-4777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sunil G updated YARN-4777:
--------------------------
Description:
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 (all common queue related validations) 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.
Its better if a common api can be exposed from YarnScheduler for this queue
validation. Now any scheduler can implement this interface and can do queue
related validation. This api can be invoked from RMAppManager so that we can
take out certain validation out from scheduler little earlier.
was:
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.
> Retrospect Queue related validation 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 (all common queue related validations) 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.
> Its better if a common api can be exposed from YarnScheduler for this queue
> validation. Now any scheduler can implement this interface and can do queue
> related validation. This api can be invoked from RMAppManager so that we can
> take out certain validation out from scheduler little earlier.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
