Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]
Created 12-07-2015 11:04 PM
for the following interfaces:
<interface type="readonly" endpoint="hftp://<host>:50070"/>
<interface type="write" endpoint="hdfs://<host>:8020" />
If we are pointing to a cluster with HDFS H/A enabled?
Created 12-09-2015 06:54 PM
There are a couple considerations that need to be taken into account when using NN HA with Falcon and Oozie. In all cases, you need to use the Namenode service ID when referring to the Namenode in the cluster xml. This value can be found in hdfs-site.xml in the property dfs.ha.namenodes.[nameservice ID]. For multi-cluster installs, you need to setup all cluster Namenode HA nameservice ID details in all clusters. For example, if you have two clusters, hdfs-site.xml for both cluster one and cluster two will have 2 nameservice IDs. Likewise, for three clusters, all three clusters would have three nameservice IDs. A two-cluster implementation would look similar to the following:
<property> <name>dfs.ha.namenodes.hacluster1</name> <value>c1nn1,c1nn2</value> </property> <property> <name>dfs.ha.namenodes.hacluster2</name> <value>c2nn1,c2nn2</value> </property>
Now, when you setup Falcon, provide both cluster definitions on both clusters.
Created 12-07-2015 11:19 PM
If the nameservice is "myHA", the interfaces should be "hdfs://myHA".
Created 12-08-2015 04:30 PM
Just to clarify, the cluster in question is different from the one where Falcon is running, i.e. it is a D/R cluster we want to copy data to..
Created 12-09-2015 03:50 PM
You can point to it directly via its address, or you can do as @bvellanki (balu) mentioned, and list its HA. For example, if your HA for your backup cluster is called DRHA, your address would be hdfs://DRHA:8020. See below:
<interface type="readonly" endpoint="hftp://DRHA.company.com:50070" version="2.2.0"/> <interface type="write" endpoint="hdfs://DRHA.company.com:8020" version="2.2.0"/> #You can also do this, depending on preference <interface type="readonly" endpoint="hftp://DRHA:50070" version="2.2.0"/> <interface type="write" endpoint="hdfs://DRHA:8020" version="2.2.0"/>
Created 12-09-2015 06:54 PM
There are a couple considerations that need to be taken into account when using NN HA with Falcon and Oozie. In all cases, you need to use the Namenode service ID when referring to the Namenode in the cluster xml. This value can be found in hdfs-site.xml in the property dfs.ha.namenodes.[nameservice ID]. For multi-cluster installs, you need to setup all cluster Namenode HA nameservice ID details in all clusters. For example, if you have two clusters, hdfs-site.xml for both cluster one and cluster two will have 2 nameservice IDs. Likewise, for three clusters, all three clusters would have three nameservice IDs. A two-cluster implementation would look similar to the following:
<property> <name>dfs.ha.namenodes.hacluster1</name> <value>c1nn1,c1nn2</value> </property> <property> <name>dfs.ha.namenodes.hacluster2</name> <value>c2nn1,c2nn2</value> </property>
Now, when you setup Falcon, provide both cluster definitions on both clusters.
Created 02-02-2016 02:35 PM
@dkjerrumgaard has this been resolved? Can you post your solution or accept best answer?