hadoop-common-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Harsh J <ha...@cloudera.com>
Subject Re: fairscheduler : group.name doesn't work, please help
Date Thu, 01 Mar 2012 17:54:54 GMT
The group.name scheduler support was introduced in
https://issues.apache.org/jira/browse/HADOOP-3892 but may have been
broken by the security changes present in 0.20.205. You'll need the
fix presented in  https://issues.apache.org/jira/browse/MAPREDUCE-2457
to have group.name support.

On Thu, Mar 1, 2012 at 6:42 PM, Austin Chungath <austincv@gmail.com> wrote:
>  I am running fair scheduler on hadoop 0.20.205.0
>
> http://hadoop.apache.org/common/docs/r0.20.205.0/fair_scheduler.html
> The above page talks about the following property
>
> *mapred.fairscheduler.poolnameproperty*
> **
> which I can set to *group.name*
> The default is user.name and when a user submits a job the fair scheduler
> assigns each user's job to a pool which has the name of the user.
> I am trying to change it to group.name so that the job is submitted to a
> pool which has the name of the user's linux group. Thus all jobs from any
> user from a specific group go to the same pool instead of an individual
> pool for every user.
> But *group.name* doesn't seem to work, has anyone tried this before?
>
> *user.name* and *mapred.job.queue.name* works. Is group.name supported in
> 0.20.205.0 because I don't see it mentioned in the docs?
>
> Thanks,
> Austin



-- 
Harsh J

Mime
View raw message