Benjamin Zhitomirsky created OOZIE-1685:
-------------------------------------------
Summary: Oozie doesn’t process correctly workflows with a
non-default name node
Key: OOZIE-1685
URL: https://issues.apache.org/jira/browse/OOZIE-1685
Project: Oozie
Issue Type: Bug
Components: core
Affects Versions: 4.0.0, 3.3.2
Environment: Any
Reporter: Benjamin Zhitomirsky
Fix For: 3.3.2
When <name-node> element in Oozie workflow specifies a name node different from
the default one (specified in core-site.xml), the following functionality
doesn’t work properly:
- Location of libraries specified via
oozie.service.WorkflowAppService.system.libpath. Oozie first (during launcher
configuration) tries to locate them using name node specified by the
<name-node> element, but later during job submission it expects this path to be
under the default Oozie name node
- Processing of the job-xml element if job xml is specified via absolute path.
Oozie tries locate it under the default Oozie name node instead of the
name-node specified in action.
Specifying non-default name node makes a lot of sense in Azure environment,
because it allows to submit the same job to different Hadoop clusters.
I will submit a fix for CR soon. Please refer attached short document for more
information.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
