It's certainly something that's present in 3.2.0, but i'm not seeing the
relevant code in HadoopAccessorService for 2.3.0 that would pick this up.

As for using workflow.xml - i was trying to avoid this as i have a good
number of coordinators, workflows and ultimately MR actions that I'd need
to update this for (unless I'm misunderstanding you - is there a 'global'
workflow.xml file i can set some default values in - i don't think there is
as this wouldn't make sense)?

Thanks

Chris


On Mon, Jul 29, 2013 at 2:12 PM, Mona Chitnis <[email protected]> wrote:

> Not entirely sure about 2.3.0 having that change. Tucu, Robert do you know
> what that change to introduce 'hadoop-conf' dir was called so it can be
> mapped to one of the release-log entries?
>
> In case, this approach won't apply to your version, you can always pass on
> configuration properties through your Oozie workflow.xml for mapred child
> JVM opts
>
> E.g.
> <action>
> Š
> <configuration>
> <property>
> <name>mapred.child.java.opts></name>
> <value>-Xmx2G</value>
> </property>
> ...
> </configuration>
> Š
> </action>
>
> NOTE: If you wish to increase the JVM size for Pig launcher job too,
> prepend "oozie.launcher." to the above property name.
>
> On 7/29/13 10:43 AM, "Chris White" <[email protected]> wrote:
>
> >Mona,
> >
> >Is this true for 2.3.0 with a war distro - i can't find any reference to
> >"hadoop-conf" while greping the src folder
> >
> >Chris
> >
> >
> >On Mon, Jul 29, 2013 at 1:36 PM, Mona Chitnis <[email protected]>
> >wrote:
> >
> >> Hi Chris,
> >>
> >> Oozie distro dir is currently built in a way that it has a 'hadoop-conf'
> >> dir underneath 'conf', which sits alongside other Oozie config files
> >>e.g.
> >> Oozie-site.xml and so on. You can put your custom hadoop *-site.xml
> >>files
> >> inside this 'hadoop-conf'.
> >>
> >> Regards,
> >> Mona
> >>
> >> On 7/29/13 10:26 AM, "Chris White" <[email protected]> wrote:
> >>
> >> >Is there a simple way to override values in the Hadoop mapred-site.xml
> >>for
> >> >all jobs run via the oozie server (rather than on a per workflow
> >>basis)?
> >> >
> >> >By default my cluster has JVM child.opts with a specific maximum JVM
> >>size
> >> >(-Xmx2G) and i want to reduce this, but only for jobs run via oozie.
> >> >
> >> >Is there some way to start oozie with an alternative HADOOP_CONF
> >> >directory?
> >> >- i've not been able to find an obvious place in my instance where the
> >> >conf
> >> >directory is configured (to override)
> >> >
> >> >(oozie-2.3.0, CDH3u1 if that makes any difference)
> >> >
> >> >Thanks
> >>
> >>
>
>

Reply via email to