[ 
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}
> <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.

Reply via email to