[
https://issues.apache.org/jira/browse/HDFS-13653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16508487#comment-16508487
]
Íñigo Goiri commented on HDFS-13653:
------------------------------------
The reason why it doesn't apply to branch-2 is {{TestHdfsConfigFields}}.
This is just a minor change.
[~ekanth], do you mind providing a branch-2 patch?
> Make dfs.client.failover.random.order a per nameservice configuration
> ---------------------------------------------------------------------
>
> Key: HDFS-13653
> URL: https://issues.apache.org/jira/browse/HDFS-13653
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: federation
> Reporter: Ekanth Sethuramalingam
> Assignee: Ekanth Sethuramalingam
> Priority: Major
> Fix For: 3.2.0, 3.1.1, 3.0.4
>
> Attachments: HDFS-13653.001.patch, HDFS-13653.002.patch,
> HDFS-13653.003.patch, HDFS-13653.004.patch, HDFS-13653.005.patch,
> HDFS-13653.006.patch, HDFS-13653.007.patch, HDFS-13653.008.patch,
> HDFS-13653.009.patch, HDFS-13653.010.patch
>
>
> Currently the dfs.client.failover.random.order is applied globally. If we
> have a combination of router and non-router nameservice, the random order
> should ideally be enabled only for the router based nameservice. This Jira is
> to make this configuration per-nameservice so that this can be configured
> independently for each nameservice.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
