hadoop-common-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brian Jeltema <bdjelt...@gmail.com>
Subject Re: mapreduce.job.running.map.limit has no effect
Date Sun, 03 Jan 2016 12:19:13 GMT
It was one job (otherwise, the question makes no sense). 
But at this point, it’s ancient history.

> On Jan 2, 2016, at 11:57 PM, Tianyin Xu <tixu@cs.ucsd.edu> wrote:
> 
> Are these 35 map tasks from one job or different jobs?
> 
> ~t
> 
> 
> On Wed, Dec 2, 2015 at 11:32 AM, Namikaze Minato <lloydsensei@gmail.com <mailto:lloydsensei@gmail.com>>
wrote:
> Looks like a bug to me :/
> 
> On 2 December 2015 at 17:49, Brian Jeltema <bdjeltema@gmail.com <mailto:bdjeltema@gmail.com>>
wrote:
> I’m running Hadoop 2.7.1. I tried to limit the number of concurrent map tasks using
> mapreduce.job.running.map.limit=5, but that property had no effect on the number
> of tasks (35 concurrently running in my case). I checked the value of that property
> in the job history, and it was set correctly. Is this a bug or have I overlooked something?
> 
> Thanks
> Brian
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@hadoop.apache.org <mailto:user-unsubscribe@hadoop.apache.org>
> For additional commands, e-mail: user-help@hadoop.apache.org <mailto:user-help@hadoop.apache.org>
> 
> 
> 
> 
> 
> -- 
> Tianyin XU,
> http://cseweb.ucsd.edu/~tixu/ <http://cseweb.ucsd.edu/%7Etixu/>

Mime
View raw message