Stopping and restarting the mapred service should push the new .xml file out, should it not? I've done 'bin/mapred-stop.sh', 'bin/mapred-start.sh', and I can see my new values in the file:.../mapred/system/job_SomeNumber_SomeNumber/job.xml files associated with the jobs. The mapred.tasktracker.map.tasks.maximum values shown in those files are 8, but each worker node tasktracker still uses the value 2. What file should contain the xml for the tasktracker itself? Does the maximum map task number get set when the task tracker is spawned, or can a new job reset the number?
Thanks, -Joel On Tue, 2008-09-23 at 11:46 -0700, Arun C Murthy wrote: > On Sep 23, 2008, at 11:41 AM, Joel Welling wrote: > > > Hi folks; > > I have a small cluster, but each node is big- 8 cores each, with lots > > of IO bandwidth. I'd like to increase the number of simultaneous map > > and reduce tasks scheduled per node from the default of 2 to something > > like 8. > > My understanding is that I should be able to do this by increasing > > mapred.tasktracker.reduce.tasks.maximum and > > mapred.tasktracker.map.tasks.maximum , but doing so does not increase > > the number of tasks. I've been running gridmix with these parameters > > set to 4, but the average number of tasks per node stays at 4, with 2 > > reduce and 2 map. > > Am I missing something? Do I need to adjust something else as well? > > > > Please ensure that _all_ machines (tasktrackers) have this updated > configuration file... the above config knobs are used by the > TaskTrackers and hence they need to have the updated configs. > > Arun > > > Thanks, > > -Joel > > [EMAIL PROTECTED] > >
