Return-Path: X-Original-To: apmail-hadoop-hdfs-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7F250DFA3 for ; Mon, 15 Oct 2012 21:27:58 +0000 (UTC) Received: (qmail 74190 invoked by uid 500); 15 Oct 2012 21:27:53 -0000 Delivered-To: apmail-hadoop-hdfs-user-archive@hadoop.apache.org Received: (qmail 74012 invoked by uid 500); 15 Oct 2012 21:27:53 -0000 Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hadoop.apache.org Delivered-To: mailing list user@hadoop.apache.org Received: (qmail 74005 invoked by uid 99); 15 Oct 2012 21:27:53 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 15 Oct 2012 21:27:53 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of silvianhadoop@gmail.com designates 209.85.212.182 as permitted sender) Received: from [209.85.212.182] (HELO mail-wi0-f182.google.com) (209.85.212.182) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 15 Oct 2012 21:27:47 +0000 Received: by mail-wi0-f182.google.com with SMTP id hm2so2174051wib.11 for ; Mon, 15 Oct 2012 14:27:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=2/xG+SiJG5XiXYWOJOQNRjjNoTzihsn07C6M6W5P2z8=; b=tnsnutbIbQOVTFqHXA5DIo5oThxm90SYkoNDh/ZXIijd9oZm8ui8MJzaOrpKZ08ZJ4 E3qyuBlLkb3XFGLciG+Tyk0d8hc6+HQts6cX6YnxV+IJRpje1VHgw3slA1X4M/4MtdqU n8QNUrTrMiI2CIR3xEUnrxCqIp4OsNiXoRZWlv7U82t0g1lVXsOTSo95fsvyC1fgEKjY b4MfsgDWUN7YVe9S8nSEC2rRTMUvMWw69gQwSA2Lgjy7F7WBISSmDuYdqZdSyEFCY893 nUKULAsBUYAul4Wg0XiiwT9gI43TMl/v3ke5J+tBkdvctWK5VhE0XLLpWk1Dw2FO5Jwj nMAA== MIME-Version: 1.0 Received: by 10.180.83.227 with SMTP id t3mr10407857wiy.13.1350336446994; Mon, 15 Oct 2012 14:27:26 -0700 (PDT) Received: by 10.194.21.228 with HTTP; Mon, 15 Oct 2012 14:27:26 -0700 (PDT) In-Reply-To: References: <6203AF4C-72E6-43C7-B712-0CF2CD63BA81@gmail.com> Date: Mon, 15 Oct 2012 14:27:26 -0700 Message-ID: Subject: Re: Fair scheduler. From: Patai Sangbutsarakum To: user@hadoop.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org Thanks for input, I am reading the document; i forget to mention that i am on cdh3u4. > If you point your poolname property to mapred.job.queue.name, then you > can leverage the Per-Queue ACLs Is that mean if i plan to 3 pools of fair scheduler, i have to configure 3 queues of capacity scheduler. in order to have each pool can leverage Per-Queue ACL of each queue.? On Sat, Oct 13, 2012 at 8:30 PM, Harsh J wrote: > If you point your poolname property to mapred.job.queue.name, then you > can leverage the Per-Queue ACLs described at > http://hadoop.apache.org/docs/stable/mapred_tutorial.html#Job+Authorization > to do user/group based control. > > In addition, depending on the version/distribution of Apache Hadoop in > use, you can set mapred.fairscheduler.allow.undeclared.pools to false > in mapred-site.xml to disallow dynamic pool names (to box users to use > specific poolnames and not get away with new ones). > > On Sun, Oct 14, 2012 at 6:03 AM, Patai Sangbutsarakum > wrote: >> Is that anyway to control who can submit job to a pool.? >> >> Eg. Pool1, can run jobs submitted from any users except userx. >> >> Userx can submit jobs to poolx only. Can't submit to pool1. >> >> Hope this make sense. >> Patai > > > > -- > Harsh J