You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-user@hadoop.apache.org by Lance Norskog <go...@gmail.com> on 2011/04/08 06:37:10 UTC
bin/daemon.sh problem with memory args
Somehow, in the long chain of shell variable fiddling that creates the
command line in bin/daemon.sh, there is a small mistake. The command
line for tasktracker comes out (shorn of many other items) with two
memory allocation requests:
/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin/java
--Xmx1000m -Xmx512m org.apache.hadoop.mapred.TaskTracker
This is in Cloudera CH3, but is probably in regular 0.20.
--
Lance Norskog
goksron@gmail.com
Re: bin/daemon.sh problem with memory args
Posted by Harsh J <ha...@cloudera.com>.
Hello Lance,
On Fri, Apr 8, 2011 at 10:07 AM, Lance Norskog <go...@gmail.com> wrote:
> Somehow, in the long chain of shell variable fiddling that creates the
> command line in bin/daemon.sh, there is a small mistake. The command
> line for tasktracker comes out (shorn of many other items) with two
> memory allocation requests:
>
> /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin/java
> --Xmx1000m -Xmx512m org.apache.hadoop.mapred.TaskTracker
Yes, this occurs when special opts are also set for individual
daemons. An issue already tracks this, if you're interested in fixing
this behavior! Have a look at:
https://issues.apache.org/jira/browse/HADOOP-6167
--
Harsh J