-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/63142/
-----------------------------------------------------------
Review request for ranger, Alok Lal, Ankita Sinha, Don Bosco Durai, Colm O
hEigeartaigh, Gautam Borad, Madhan Neethiraj, pengjianhua, Ramesh Mani,
Selvamohan Neethiraj, Velmurugan Periasamy, and Qiang Zhang.
Bugs: RANGER-1844
https://issues.apache.org/jira/browse/RANGER-1844
Repository: ranger
Description
-------
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?
Diffs
-----
hdfs-agent/src/main/java/org/apache/ranger/services/hdfs/client/HdfsClient.java
c252213f
Diff: https://reviews.apache.org/r/63142/diff/1/
Testing
-------
Thanks,
Qiang Zhang
