Can I setup Oozie to works with several Namenodes and Jobtrackers?

[Pedro Sá da Costa <ps...@gmail.com>]

Can I setup Oozie to works with several Namenodes and Jobtrackers?

-- 
Best regards,

Re: Can I setup Oozie to works with several Namenodes and Jobtrackers?

[Matt Goeke <go...@gmail.com>]

*Quick answer: *

Yes

*Long answer: *

You can configure this at several levels but the easiest way is to define a
jobtracker and namenode var in your properties submission and pass this
down [through the coordinator] to the workflow. Inside of the workflow you
can then reference it doing something like:

...
<java>
      <job-tracker>${JOB_TRACKER}</job-tracker>
      <name-node>${NAME_NODE}</name-node>
      ...
</java>
...

Assuming you need a workflow to access multiple clusters you can actually
use the example above to specify different clusters per action. I haven't
done this before in any of my scripts so one thing you probably need to
watch out for is that the [coordinator and] workflow .xml files may need to
be present on the HDFS instance you are referencing.

--
Matt


On Wed, Apr 24, 2013 at 8:45 AM, Pedro Sá da Costa <ps...@gmail.com>wrote:

> Can I setup Oozie to works with several Namenodes and Jobtrackers?
>
> --
> Best regards,
>