Hey Keith,
Sorry for the late response here (I had meant to reply but I believe I
got distracted and forgot all about it):
I agree with you on all counts. The config is indeed for service-level
slots. My reply was to only correct Kartheek's assumptions.
Regarding documentation - I'd love to be a
On Jun 6, 2012, at 03:42 , Harsh J wrote:
>> I think mapred.tasktracker.map.tasks.maximum sets the number of map
> tasks and not slots.
>
> This is incorrect. The property does configure slots. Please also see
> http://wiki.apache.org/hadoop/HowManyMapsAndReduces and
> http://wiki.apache.org/had
> I think mapred.tasktracker.map.tasks.maximum sets the number of map
tasks and not slots.
This is incorrect. The property does configure slots. Please also see
http://wiki.apache.org/hadoop/HowManyMapsAndReduces and
http://wiki.apache.org/hadoop/FAQ#I_see_a_maximum_of_2_maps.2BAC8-reduces_spawned
I think mapred.tasktracker.map.tasks.maximum sets the number of map
tasks and not slots.
Keith, so that means per core, if I specify the maximum number of map
tasks it can host, whether all the maps per slot will run parallely or
they execute one after the other?. I understand that maps that are
sc
Hi,
You can change the no of slots using the following properties in
mapred-site.xml.
1. mapred.tasktracker.map.tasks.maximum ( for map slots)
2. mapred.tasktracker.reduce.tasks.maximum (for reduce slot)
On Tue, Jun 5, 2012 at 3:44 AM, Keith Wiley wrote:
> The number of slots correspo
The number of slots corresponds to the number of cores (e.g., a 10-node cluster
consisting of quad-core cpus has 40 cores and therefore 40 slots). The slots
can be divided amongst the maps and reduces in a way which integer-divides into
the cores of a single machine. So if the nodes are quad-c
