Return-Path: 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 7F6161845F for ; Thu, 1 Oct 2015 05:54:06 +0000 (UTC) Received: (qmail 51530 invoked by uid 500); 1 Oct 2015 05:54:06 -0000 Delivered-To: apmail-falcon-dev-archive@falcon.apache.org Received: (qmail 51482 invoked by uid 500); 1 Oct 2015 05:54:06 -0000 Mailing-List: contact dev-help@falcon.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@falcon.apache.org Delivered-To: mailing list dev@falcon.apache.org Received: (qmail 51471 invoked by uid 99); 1 Oct 2015 05:54:06 -0000 Received: from Unknown (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Oct 2015 05:54:06 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id E7DFCC0182 for ; Thu, 1 Oct 2015 05:54:05 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.974 X-Spam-Level: X-Spam-Status: No, score=0.974 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.006] autolearn=disabled Received: from mx1-us-west.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id xwnzCrIeapcg for ; Thu, 1 Oct 2015 05:54:05 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with SMTP id 09653202AF for ; Thu, 1 Oct 2015 05:54:05 +0000 (UTC) Received: (qmail 51283 invoked by uid 99); 1 Oct 2015 05:54:04 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Oct 2015 05:54:04 +0000 Date: Thu, 1 Oct 2015 05:54:04 +0000 (UTC) From: "Peeyush Bishnoi (JIRA)" To: dev@falcon.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (FALCON-1503) cluster mirroring 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-1503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14939356#comment-14939356 ] Peeyush Bishnoi commented on FALCON-1503: ----------------------------------------- For running the HiveDR to mirror Hive data and metadata, it is must to have thrift and hive2 server on BigInsights. Once you have services((hive2,thrift,HDFS)) details for BigInsights and HDP sandbox, add it to hive-disaster-recovery.properties and then invoke hive-disaster-recovery recipe command. >From the doc link which you have shared in that it looks like that Hive (thrift) is running on port 10000 but there is no mention on hive2. > cluster mirroring > ------------------ > > Key: FALCON-1503 > URL: https://issues.apache.org/jira/browse/FALCON-1503 > Project: Falcon > Issue Type: Bug > Affects Versions: 0.6.1 > Environment: Hortonworks 2.3 sandbox > BigInsights 3.0.2 sandbox > Reporter: mpopa > > Hi, > I've been trying to setup mirroring between two clusters. > One runs BigInsights 3.0.2, the other Hortonworks 2.3. > I'm running Falcon on the Hortonworks cluster (which is actually just a sandbox). > I have no trouble defining the target cluster (on the localhost), but cannot define the source > cluster (on the remote BigInsights install). > The problem is with the "execute" interface; I've tried a series of ports starting with 9000 > which is the default namenode, 9001, 50030. > > (I do have a DNS entry for bivm.ibm.com) > The error that I get is: > org.apache.falcon.entity.parser.ValidationException: Invalid Execute server or port: bivm.ibm.com:50030 > It seems like this version of BIgInsights does not come with Yarn, and from what I see, the execute interface tries to connect to yarn's port. > Any insight (pun intended) is greatly appreciated. > thank you in advance > mihai popa -- This message was sent by Atlassian JIRA (v6.3.4#6332)