You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ranger.apache.org by "Qiang Zhang (JIRA)" <ji...@apache.org> on 2017/10/19 11:13:00 UTC
[jira] [Created] (RANGER-1844) Ranger admin support hdfs HA
configuration when creating hdfs service.
Qiang Zhang created RANGER-1844:
-----------------------------------
Summary: Ranger admin support hdfs HA configuration when creating hdfs service.
Key: RANGER-1844
URL: https://issues.apache.org/jira/browse/RANGER-1844
Project: Ranger
Issue Type: Bug
Components: plugins, Ranger
Affects Versions: master
Reporter: Qiang Zhang
Assignee: Qiang Zhang
In ranger admin, when creating a hdfs service, if hdfs cluster is in HA mode,you have to config a lot of configs in hdfs_dev,such as:
Namenode URL *=hdfs://hdfscluster
===Add New Configurations===
dfs.nameservices=hdfscluster
dfs.client.failover.proxy.provider.hdfscluster=org.apache.hadoop.hdfs.server.namenode.ha.ConfiguredFailoverProxyProvider
dfs.ha.namenodes.hdfscluster=nn1,nn2
dfs.namenode.rpc-address.hdfscluster.nn1=hdfs://10.43.159.240:9000
dfs.namenode.rpc-address.hdfscluster.nn2=hdfs://10.43.159.245:9000
===End of add New Configurations===
And other big data components such as hbase,hive and so on can support HA without config
lots of "Add New Configurations",it is easy to config a url. like zk queue configuration in hbase ,like jdbc url in hive. In hdfs service, only need to config "fs.default.name" :
Namenode URL *=hdfs://hdfscluster old
Namenode URL *=hdfs://dap230-183:9000,hdfs://dap229-183:9000 new
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)