You are viewing a plain text version of this content. The canonical link for it is here.

Posted to yarn-dev@hadoop.apache.org by "Sunil G (JIRA)" <ji...@apache.org> on 2016/03/08 17:53:40 UTC

[jira] [Created] (YARN-4777) Retrospect Non-Existent Queue check and its error handling while submitting a new application

Sunil G created YARN-4777:
-----------------------------

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