hadoop-common-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Austin Chungath <austi...@gmail.com>
Subject fairscheduler : group.name | Please edit patch to work for 0.20.205
Date Mon, 05 Mar 2012 12:57:07 GMT
Can someone have a look at the patch MAPREDUCE-2457 and see if it can be
modified to work for 0.20.205?
I am very new to java and have no idea what's going on in that patch. If
you have any pointers for me, I will see if I can do it on my own.

Thanks,
Austin

On Fri, Mar 2, 2012 at 7:15 PM, Austin Chungath <austincv@gmail.com> wrote:

> I tried the patch MAPREDUCE-2457 but it didn't work for my hadoop 0.20.205.
> Are you sure this patch will work for 0.20.205?
> According to the description it says that the patch works for 0.21 and
> 0.22 and it says that 0.20 supports group.name without this patch...
>
> So does this patch also apply to 0.20.205?
>
> Thanks,
> Austin
>
>  On Thu, Mar 1, 2012 at 11:24 PM, Harsh J <harsh@cloudera.com> wrote:
>
>> 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
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message