Interesting! Here's what the Condor folks have been doing with MapReduce:
http://www.cs.wisc.edu/condor/CondorWeek2010/condor-presentations/thain-condor-hadoop.pdf
Dunno why we don't see more of them (maybe it's just because I'm not subscribed
to the MAPREDUCE mailing list? I have too many ema
They have gotten lots of mileage out of breaking the scheduling and
the resource provision into two different components. Having
multiple jobtrackers would be very advantageous if it didn't require
you to partition your pool.
https://issues.apache.org/jira/browse/MAPREDUCE-279
Arun
On Apr 28, 2010, at 5:04 AM, Steve Loughran wrote:
> prajyot bankade wrote:
>> Hello Everyone,
>> I have just started reading about hadoop job tracker. In one book I read
>> that there is only one job tracker who is responsible to distribute task to
>> worker system. Please make me right if i say
prajyot bankade wrote:
Hello Everyone,
I have just started reading about hadoop job tracker. In one book I read
that there is only one job tracker who is responsible to distribute task to
worker system. Please make me right if i say some thing wrong.
I have few questions,
why there is only one
Hello Everyone,
I have just started reading about hadoop job tracker. In one book I read
that there is only one job tracker who is responsible to distribute task to
worker system. Please make me right if i say some thing wrong.
I have few questions,
why there is only one job tracker?
What will h
