Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Duplicate
-
None
-
None
-
None
-
None
Description
Replication between secure clusters still fails even after having applied the patch unless the following property is added to replication-action.xml
<property>
<name>oozie.launcher.mapreduce.job.hdfs-servers</name>
<value><namenode for source cluster>,${namenode for target cluster}</value>
</property>
The tests might pass if this property is set on the oozie server in oozie-site.xml but I don't suppose that it'd be desirable to update oozie-site.xml every time a replication job is submitted.
Currently, the workaround I have for replication via hcat jobs is to add this property with variables falconSourceNameNode and falconTargetNameNode that is as follows:
<property>
<name>oozie.launcher.mapreduce.job.hdfs-servers</name>
<value>${falconSourceNameNode},${falconTargetNameNode}</value>
</property>
However these variables aren't available for simple replication jobs (i.e. no hcat).
Attachments
Issue Links
- duplicates
-
FALCON-1282 Incorrect hdfs servers property for feed replication in secured environment
- Resolved