You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Íñigo Goiri (JIRA)" <ji...@apache.org> on 2018/06/04 22:16:00 UTC
[jira] [Updated] (HDFS-13653) Make dfs.client.failover.random.order
a per nameservice configuration
[ https://issues.apache.org/jira/browse/HDFS-13653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Íñigo Goiri updated HDFS-13653:
-------------------------------
Summary: Make dfs.client.failover.random.order a per nameservice configuration (was: [RBF] Make dfs.client.failover.random.order a per nameservice configuration)
> 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: Sub-task
> Components: federation
> Reporter: Ekanth S
> Assignee: Ekanth S
> Priority: Major
> Attachments: HDFS-13653.001.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-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org