Return-Path: 
 <mapreduce-issues-return-5902-apmail-hadoop-mapreduce-issues-archive=hadoop.apache.org@hadoop.apache.org>
Delivered-To: apmail-hadoop-mapreduce-issues-archive@minotaur.apache.org
Received: (qmail 66006 invoked from network); 3 Nov 2009 03:56:24 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 3 Nov 2009 03:56:24 -0000
Received: (qmail 12341 invoked by uid 500); 3 Nov 2009 03:56:23 -0000
Delivered-To: apmail-hadoop-mapreduce-issues-archive@hadoop.apache.org
Received: (qmail 12271 invoked by uid 500); 3 Nov 2009 03:56:23 -0000
Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:mapreduce-issues-help@hadoop.apache.org>
List-Unsubscribe: <mailto:mapreduce-issues-unsubscribe@hadoop.apache.org>
List-Post: <mailto:mapreduce-issues@hadoop.apache.org>
List-Id: <mapreduce-issues.hadoop.apache.org>
Reply-To: mapreduce-issues@hadoop.apache.org
Delivered-To: mailing list mapreduce-issues@hadoop.apache.org
Received: (qmail 12258 invoked by uid 99); 3 Nov 2009 03:56:22 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Nov 2009 03:56:22 +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; Tue, 03 Nov 2009 03:56:19 +0000
Received: from brutus (localhost [127.0.0.1])
	by brutus.apache.org (Postfix) with ESMTP id 5CB6A234C4A7
	for <mapreduce-issues@hadoop.apache.org>;
 Mon,  2 Nov 2009 19:55:59 -0800 (PST)
Message-ID: <421047793.1257220559365.JavaMail.jira@brutus>
Date: Tue, 3 Nov 2009 03:55:59 +0000 (UTC)
From: "Matei Zaharia (JIRA)" <jira@apache.org>
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=12772869#action_12772869 ] 

Matei Zaharia commented on MAPREDUCE-707:
-----------------------------------------

I should also add that my original intent in the JIRA was to have a separate way of setting the pool that doesn't require using the mapred.fairscheduler.poolnameproperty. This way, users could set poolnameproperty to something else (e.g. group.name for a Unix group). However, I think it's overkill to add a second way of setting the pool name, so I'd be okay with just a patch to mapred-default.xml if that works.

> 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}
> <property>
>   <name>mapred.fairscheduler.poolnameproperty</name>
>   <value>pool.name</value>
> </property>
> <property>
>   <name>pool.name</name>
>   <value>${user.name}</value>
> </property>
> {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.