hadoop-mapreduce-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "GOEKE, MATTHEW (AG/1000)" <matthew.go...@monsanto.com>
Subject RE: FairScheduler Local Task Restriction
Date Thu, 22 Sep 2011 20:05:57 GMT
If you dig into the job history on the web-ui can you confirm whether it is the same 16 tasktrackers
slots that are getting the map tasks? Long shot but it could be that it is actually distributing
across your cluster and there is some other issue that is springing up. Also, how long does
each of your map tasks take?


From: Adam Shook [mailto:ashook@clearedgeit.com]
Sent: Thursday, September 22, 2011 2:41 PM
To: mapreduce-user@hadoop.apache.org
Subject: FairScheduler Local Task Restriction

Hello All,

I have recently switched my small Hadoop dev cluster (v0.20.1) to use the FairScheduler. 
I have a max of 128 map tasks available and recently noticed that my jobs seem to use a maximum
of 16 at any given time (the job I am looking at in particular runs for about 15 minutes)
- they are also all data local map tasks.  I searched around a bit and discovered the mapred.fairscheduler.locality.delay
may be to blame.  I set it to 0 in mapred-site.xml, copied the file around to my nodes and
tried running another job.  It still has 16 tasks.

Does it require a cluster restart?  Is it something totally different?  Should I not set this
value to zero?


-- Adam
This e-mail message may contain privileged and/or confidential information, and is intended
to be received only by persons entitled
to receive such information. If you have received this e-mail in error, please notify the
sender immediately. Please delete it and
all attachments from any servers, hard drives or any other media. Other use of this e-mail
by you is strictly prohibited.

All e-mails and attachments sent and received are subject to monitoring, reading and archival
by Monsanto, including its
subsidiaries. The recipient of this e-mail is solely responsible for checking for the presence
of "Viruses" or other "Malware".
Monsanto, along with its subsidiaries, accepts no liability for any damage caused by any such
code transmitted by or accompanying
this e-mail or any attachment.

The information contained in this email may be subject to the export control laws and regulations
of the United States, potentially
including but not limited to the Export Administration Regulations (EAR) and sanctions regulations
issued by the U.S. Department of
Treasury, Office of Foreign Asset Controls (OFAC).  As a recipient of this information you
are obligated to comply with all
applicable U.S. export laws and regulations.

View raw message