[RANGER-1752] When "dfs.nameservices" configures multiple nameservice id and then test hdfs connection, verifying "dfs.client.failover.proxy.provider.[dfs.nameservices]" is incorrect

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.0.0
• Fix Version/s: 1.0.0, master
• Component/s: plugins
• Labels: patch
• Flags: Patch
• Assignee: peng.jianhua
• Reporter: peng.jianhua
• Created: 25/Aug/17 02:57
• Updated: 08/Sep/17 01:57
• Resolved: 08/Sep/17 01:57

Description

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]

Issue Links

• links to: https://reviews.apache.org/r/61909/