[
https://issues.apache.org/jira/browse/HDFS-13653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16504887#comment-16504887
]
Íñigo Goiri commented on HDFS-13653:
------------------------------------
Thanks [~ekanth] for [^HDFS-13653.008.patch].
The test looks good.
In createAnswer and createFactory, we may have to may to make the parameters
final.
I remember that in branch-2 or so, this gave issues (BTW, can you test with
branch-2?).
I have the feeling that TestHdfsConfigFields might be related, I haven't seen
it failing in other JIRAs.
> 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
>
>
> 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]
