From yarn-issues-return-89612-apmail-hadoop-yarn-issues-archive=hadoop.apache.org@hadoop.apache.org Mon Jun 27 16:22:52 2016 Return-Path: X-Original-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id AFB3919EBB for ; Mon, 27 Jun 2016 16:22:52 +0000 (UTC) Received: (qmail 71593 invoked by uid 500); 27 Jun 2016 16:22:52 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 71554 invoked by uid 500); 27 Jun 2016 16:22:52 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 71225 invoked by uid 99); 27 Jun 2016 16:22:52 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 27 Jun 2016 16:22:52 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 2CEF92C1F6B for ; Mon, 27 Jun 2016 16:22:52 +0000 (UTC) Date: Mon, 27 Jun 2016 16:22:52 +0000 (UTC) From: "Prabhu Joseph (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-5295) YARN queue-mappings to check Queue is present before submitting job MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/YARN-5295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15351347#comment-15351347 ] Prabhu Joseph commented on YARN-5295: ------------------------------------- [~sunilg] Yes, if test queue is present, the application submitted by test user placed into test queue. But if test queue is not present or if test queue is not a leaf queue or if test user does not have either Submit_Applications or Administer_Queue ACL, then the application is rejected. Instead, the getMappedQueue in CapacityScheduler can do the three sanity checks and return a valid queue that is platform instead of test. (Assuming test user passes the sanity checks on platform Queue) Currently the sanity checks are done separately after deciding the queue to be placed, instead sanity checks can be included in getMappedQueue logic, where once queue mapping is chosen from the list, the sanity checks can be done and if it fails, then move to the next queue mapping in the list. > YARN queue-mappings to check Queue is present before submitting job > ------------------------------------------------------------------- > > Key: YARN-5295 > URL: https://issues.apache.org/jira/browse/YARN-5295 > Project: Hadoop YARN > Issue Type: Bug > Components: capacity scheduler > Affects Versions: 2.7.2 > Reporter: Prabhu Joseph > > In yarn Queue-Mappings, Yarn should check if the queue is present before submitting the job. If not present it should go to next mapping available. > For example if we have > yarn.scheduler.capacity.queue-mappings=u:%user:%user,g:edw:platform > and I submit job with user "test" and if there is no "test" queue then it should check the second mapping (g:edw:platform) in the list and if test is part of edw group it should submit job in platform queue. > Below Sanity checks has to be done for the mapped queue in the list and if it fails then the the next queue mapping has to be chosen, when there is no queue mapping passing the sanity check, only then the application has to be Rejected. > 1. is queue present > 2. is queue not a leaf queue > 3. is user either have ACL Submit_Applications or Administer_Queue of the queue. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: yarn-issues-help@hadoop.apache.org