On 9/17/07, Ted Dunning <[EMAIL PROTECTED]> wrote: > > I have found that this parameter tends to be the limiting factor: > > <property> > <name>mapred.tasktracker.tasks.maximum</name> > <value>3</value> > <description>The maximum number of tasks that will be run > simultaneously by a task tracker. > </description> > </property> > > > There are several competing constraints at work which makes it kind of hard > to determine just how many map tasks will be run.
Awesome, thanks! Changing that parameter did indeed lift the concurrency limit for mappers. Thanks again :) Note to anyone else using EC2 as their platform: 15 is too high for this value ;-) -- Toby DiPasquale
