Re: map container is assigned default memory size rather than user configured which will cause TaskAttempt failure

Hi, How about checking the value of mapreduce.map.java.opts? Are your JVMs launched with assumed heap memory? On Thu, Oct 24, 2013 at 11:31 AM, Manu Zhang owenzhang1...@gmail.com wrote: Just confirmed the problem still existed even the mapred-site.xmls on all nodes have the same configuration

Re: map container is assigned default memory size rather than user configured which will cause TaskAttempt failure

My mapreduce.map.java.opts is 1024MB Thanks, Manu On Thu, Oct 24, 2013 at 3:11 PM, Tsuyoshi OZAWA ozawa.tsuyo...@gmail.comwrote: Hi, How about checking the value of mapreduce.map.java.opts? Are your JVMs launched with assumed heap memory? On Thu, Oct 24, 2013 at 11:31 AM, Manu Zhang

map container is assigned default memory size rather than user configured which will cause TaskAttempt failure

Hi, I've been running Terasort on Hadoop-2.0.4. Every time there is s a small number of Map failures (like 4 or 5) because of container's running beyond virtual memory limit. I've set mapreduce.map.memory.mb to a safe value (like 2560MB) so most TaskAttempt goes fine while the values of those