[
https://issues.apache.org/jira/browse/HDFS-13653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16505282#comment-16505282
]
Ekanth Sethuramalingam commented on HDFS-13653:
-----------------------------------------------
Thanks [~elgoiri] for the comments and pointing out the TestHdfsConfigFields
failure being related. I have address your comments and fixed the
TestHdfsConfigFields test. I also tested the patch against branch-2. It worked
fine. Let me know if you need that patch as well. New trunk patch here:
[^HDFS-13653.009.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
> 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
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
