We will have to fall back to parameterization if there is no method for passing a config file for the launcher. However, we would like to avoid taking the parameterization path if possible, so that if we find that we need to alter which properties are being passed to our launcher, we can do this without have to release a new version of our workflow.
On Thu, Aug 6, 2015 at 8:57 AM, Oussama Chougna <[email protected]> wrote: > Is parametrizing the memory values an option for you, as in: > <property> > <name>oozie.launcher.mapreduce.map.memory.mb</name> > <value>${mapMemoryMb}</value> > </property> > job.properties: > mapMemoryMb=4096 > > Cheers, > > Oussama Chougna > > > Date: Thu, 6 Aug 2015 08:38:59 -0500 > > Subject: Specifying launcher configuration > > From: [email protected] > > To: [email protected] > > > > I am attempting to specify launcher configuration for a java action. I am > > using Oozie 4.1.0. I noticed that when I set the job configuration > > (specifically memory setting/java options) in the config tags in the > > workflow's action definition[1], and prefix the settings with > > oozie.launcher, all seems to work as planned. However, if I set those > same > > properties in an xml file and use the <job-xml/> tag, those properties do > > not seem to be applied to the launcher. Based on the documentation, this > > seems like surprising behavior. We would like to be able to provide a > > dynamic config file to our java action so we won't have to release our > > workflow each time we want to add/remove launcher configuration > properties. > > Is there any method to do this? > > > > Thanks! > > > > > > [1] > > <configuration> > > <property> > > <name>oozie.launcher.mapreduce.map.memory.mb</name> > > <value>4096</value> > > </property> > > <property> > > <name>oozie.launcher.mapreduce.map.java.opts</name> > > <value>-Djava.net.preferIPv4Stack=true -Xmx3072m</value> > > </property> > > </configuration> > >
