falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Balu Vellanki (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (FALCON-1199) Patch Falcon-1129 doesn't seem to be working
Date Wed, 29 Jul 2015 22:30:05 GMT

     [ https://issues.apache.org/jira/browse/FALCON-1199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Balu Vellanki reassigned FALCON-1199:

    Assignee: Balu Vellanki

> 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
>            Assignee: Balu Vellanki
> 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
>             </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

View raw message