[
https://issues.apache.org/jira/browse/FALCON-1503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14937952#comment-14937952
]
mpopa commented on FALCON-1503:
-------------------------------
Hi Peeyush,
I've tried to configure the recipes.
A few things that I noticed:
- in the properties file I have:
sourceMetastoreUri=thrift://bivm.ibm.com:9083
the 9083 port is not open on the bigInsights cluster
sourceNN=hdfs://bivm.ibm.com:8020
the 8020 port is also not available
In spite of the obvious port issues, I tried to submit the recipe:
[falcon@sandbox ~]$ falcon recipe -name hive-disaster-recovery.xml
ERROR: Missing argument : operation
I get the operation missing error. The CLI document does not specify any
operation param for recipes.
thank you
> 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.
> <interface type='execute' endpoint='bivm.ibm.com:50030' version='2.2.0'/>
> (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)
