peng.jianhua created RANGER-1752:
------------------------------------
Summary: When "dfs.nameservices" configures multiple nameservice
id and then test hdfs connection, verifying
"dfs.client.failover.proxy.provider.[dfs.nameservices]" is incorrect
Key: RANGER-1752
URL: https://issues.apache.org/jira/browse/RANGER-1752
Project: Ranger
Issue Type: Bug
Components: plugins
Affects Versions: 1.0.0
Reporter: peng.jianhua
Assignee: peng.jianhua
Priority: Minor
When "dfs.nameservices" configures multiple nameservice id
(dfs.nameservices=nameservice1,nameservice2) and then test hdfs connection,
the code will check
"dfs.client.failover.proxy.provider.nameservice1,nameservice2" to be mandatory,
but this is incorrect.
We should check "dfs.client.failover.proxy.provider.nameservice1" and
"dfs.client.failover.proxy.provider.nameservice2" to be mandatory, respectively.
Some other configuration items are the same:
dfs.ha.namenodes.[nameservice ID]
dfs.namenode.rpc-address.[nameservice ID]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
