[
https://issues.apache.org/jira/browse/RANGER-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
peng.jianhua updated RANGER-1752:
---------------------------------
Attachment: 0001-RANGER-1752-When-dfs.nameservices-configures-multipl.patch
> 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
> Labels: patch
> Attachments:
> 0001-RANGER-1752-When-dfs.nameservices-configures-multipl.patch
>
>
> 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)
