Return-Path: 
 <dev-return-13392-apmail-falcon-dev-archive=falcon.apache.org@falcon.apache.org>
X-Original-To: apmail-falcon-dev-archive@minotaur.apache.org
Delivered-To: apmail-falcon-dev-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id BF5F81800E
	for <apmail-falcon-dev-archive@minotaur.apache.org>;
 Wed, 29 Jul 2015 22:30:07 +0000 (UTC)
Received: (qmail 33709 invoked by uid 500); 29 Jul 2015 22:30:07 -0000
Delivered-To: apmail-falcon-dev-archive@falcon.apache.org
Received: (qmail 33661 invoked by uid 500); 29 Jul 2015 22:30:07 -0000
Mailing-List: contact dev-help@falcon.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@falcon.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@falcon.apache.org>
List-Post: <mailto:dev@falcon.apache.org>
List-Id: <dev.falcon.apache.org>
Reply-To: dev@falcon.apache.org
Delivered-To: mailing list dev@falcon.apache.org
Received: (qmail 33645 invoked by uid 99); 29 Jul 2015 22:30:07 -0000
Received: from Unknown (HELO spamd2-us-west.apache.org) (209.188.14.142)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 29 Jul 2015 22:30:07 +0000
Received: from localhost (localhost [127.0.0.1])
	by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org)
 with ESMTP id 341D21A8BB0
	for <dev@falcon.apache.org>; Wed, 29 Jul 2015 22:30:07 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org
X-Spam-Flag: NO
X-Spam-Score: 0.97
X-Spam-Level: 
X-Spam-Status: No, score=0.97 tagged_above=-999 required=6.31
	tests=[KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_MSPIKE_H3=-0.01,
	RCVD_IN_MSPIKE_WL=-0.01, T_RP_MATCHES_RCVD=-0.01] autolearn=disabled
Received: from mx1-us-east.apache.org ([10.40.0.8])
	by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new,
 port 10024)
	with ESMTP id mPmHT92oD2e8 for <dev@falcon.apache.org>;
	Wed, 29 Jul 2015 22:30:06 +0000 (UTC)
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with
 SMTP id 16DBB43817
	for <dev@falcon.incubator.apache.org>; Wed, 29 Jul 2015 22:30:06 +0000 (UTC)
Received: (qmail 33631 invoked by uid 99); 29 Jul 2015 22:30:05 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 29 Jul 2015 22:30:05 +0000
Date: Wed, 29 Jul 2015 22:30:05 +0000 (UTC)
From: "Balu Vellanki (JIRA)" <jira@apache.org>
To: dev@falcon.incubator.apache.org
Message-ID: <JIRA.12827846.1430952457000.324800.1438209005359@Atlassian.JIRA>
In-Reply-To: <JIRA.12827846.1430952457000@Atlassian.JIRA>
References: <JIRA.12827846.1430952457000@Atlassian.JIRA>
 <JIRA.12827846.1430952457644@arcas>
Subject: [jira] [Assigned] (FALCON-1199) Patch Falcon-1129 doesn't seem to
 be working
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


     [ 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 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)