You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@falcon.apache.org by "Mahak (JIRA)" <ji...@apache.org> on 2015/05/07 00:47:59 UTC
[jira] [Created] (FALCON-1199) Patch Falcon-1129 doesn't seem to be
working
Mahak created FALCON-1199:
-----------------------------
Summary: Patch Falcon-1129 doesn't seem to be working
Key: FALCON-1199
URL: https://issues.apache.org/jira/browse/FALCON-1199
Project: Falcon
Issue Type: Bug
Reporter: Mahak
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).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)