This repository has been archived by the owner on Apr 5, 2022. It is now read-only.
Add support for namenode HA #6
Labels
Comments
jvalkeal
added a commit
that referenced
this issue
Jul 21, 2015
- relates to #6 - we basically detect if namenode ha is enabled which in ambari is done via a wizard after an initial cluster provisioning. - we modify both hadoop.properties and xd-shell.init for below settings(I named my ha as 'mycluster'): dfs.ha.automatic-failover.enabled=True dfs.nameservices=mycluster dfs.client.failover.proxy.provider.mycluster=org.apache.hadoop.hdfs.server.namenode.ha.ConfiguredFailoverProxyProvider dfs.ha.namenodes.mycluster=nn1,nn2 dfs.namenode.rpc-address.mycluster.nn2=ambari-3.localdomain:8020 dfs.namenode.rpc-address.mycluster.nn1=ambari-2.localdomain:8020
jvalkeal
added a commit
that referenced
this issue
Jul 30, 2015
- relates to #6 - we basically detect if namenode ha is enabled which in ambari is done via a wizard after an initial cluster provisioning. - we modify both hadoop.properties and xd-shell.init for below settings(I named my ha as 'mycluster'): dfs.ha.automatic-failover.enabled=True dfs.nameservices=mycluster dfs.client.failover.proxy.provider.mycluster=org.apache.hadoop.hdfs.server.namenode.ha.ConfiguredFailoverProxyProvider dfs.ha.namenodes.mycluster=nn1,nn2 dfs.namenode.rpc-address.mycluster.nn2=ambari-3.localdomain:8020 dfs.namenode.rpc-address.mycluster.nn1=ambari-2.localdomain:8020
|
In hadoop.properties.j2 Should be: |
|
should be fixed now, closing. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Ok, so, if HA is enabled a custom configuration is needed. HA is silently handled by a hadoop dfs client but configuration is still needed. We don't have any custom tweaks in SHDP for this but we just need to write a different xd container/shell config depending if HA is enabled.
The text was updated successfully, but these errors were encountered: