Return-Path: Delivered-To: apmail-hadoop-mapreduce-issues-archive@minotaur.apache.org Received: (qmail 56857 invoked from network); 4 Nov 2009 18:29:55 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 4 Nov 2009 18:29:55 -0000 Received: (qmail 5968 invoked by uid 500); 4 Nov 2009 18:29:55 -0000 Delivered-To: apmail-hadoop-mapreduce-issues-archive@hadoop.apache.org Received: (qmail 5928 invoked by uid 500); 4 Nov 2009 18:29:54 -0000 Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: mapreduce-issues@hadoop.apache.org Delivered-To: mailing list mapreduce-issues@hadoop.apache.org Received: (qmail 5918 invoked by uid 99); 4 Nov 2009 18:29:54 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Nov 2009 18:29:54 +0000 X-ASF-Spam-Status: No, hits=-10.5 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Nov 2009 18:29:52 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 8AC4C234C04C for ; Wed, 4 Nov 2009 10:29:32 -0800 (PST) Message-ID: <1513533319.1257359372551.JavaMail.jira@brutus> Date: Wed, 4 Nov 2009 18:29:32 +0000 (UTC) From: "Matei Zaharia (JIRA)" To: mapreduce-issues@hadoop.apache.org Subject: [jira] Commented: (MAPREDUCE-707) Provide a jobconf property for explicitly assigning a job to a pool In-Reply-To: <1603395329.1246815014830.JavaMail.jira@brutus> 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/MAPREDUCE-707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12773594#action_12773594 ] Matei Zaharia commented on MAPREDUCE-707: ----------------------------------------- The reason I haven't made the PoolManager methods call updateDemand is that FairScheduler.update() does other things as well, and doing updateDemand without doing a full update() could potentially break some of the algorithms. (I'm not sure that it does so right now, but it would have been a problem in earlier versions). Therefore, I wanted all the updates to always happen through FairScheduler.update(). I'd rather not make the PoolManager call update() all the time because it would be better if the PoolManager didn't have to be modified whenever the structure of FairScheduler changes. All of the other unit tests call update() too, so I think it's fine not to do it in setPool. > Provide a jobconf property for explicitly assigning a job to a pool > ------------------------------------------------------------------- > > Key: MAPREDUCE-707 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-707 > Project: Hadoop Map/Reduce > Issue Type: New Feature > Components: contrib/fair-share > Reporter: Matei Zaharia > Priority: Trivial > > A common use case of the fair scheduler is to have one pool per user, but then to define some special pools for various production jobs, import jobs, etc. Therefore, it would be nice if jobs went by default to the pool of the user who submitted them, but there was a setting to explicitly place a job in another pool. Today, this can be achieved through a sort of trick in the JobConf: > {code} > > mapred.fairscheduler.poolnameproperty > pool.name > > > pool.name > ${user.name} > > {code} > This JIRA proposes to add a property called mapred.fairscheduler.pool that allows a job to be placed directly into a pool, avoiding the need for this trick. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.