Mapred.child.java.opts would work as this setting applies the java.opts to both mappers and reducers. In case of java-action, it is a single map task. No need for oozie.launcher.mapred.child.java.opts unless you want the launcher job also to be passed custom options e.g. -server -Djava.net.preferIPv4Stack=true
On 8/22/14, 7:11 AM, "Bharath Kumar" <[email protected]> wrote: >Hi all, > >I am using a custom action which is extension of java action , but I >cannot set java-opts . > >So my query is if setting map.child.java.opts has similar effect as >java-opts > >because from the code of JavaActionExecuter i read its mapped to >mapred.child.java.opts > >or its the oozie.launcher.mapred.child.java.opts property I need to set. > >Here is how my workflow looks like > ><job-tracker>abc.com:9001</job-tracker> > <name-node>hdfs://abc.com:9000</name-node> > <configuration> > <property> > <name>mapred.child.java.opts</name> > <value>-Xmx5G -Xms2G</value> > </property> > <property> > <name>oozie.launcher.mapred.child.java.opts</name> > <value>-Xmx5G -Xms2G</value> > </property> > <property> > <name>mapred.compress.map.output</name> > <value>true</value> > </property> > <property> > <name>mapred.job.queue.name</name> > <value>default</value> > </property> > </configuration>
