hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ekanth Sethuramalingam (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-13653) Make dfs.client.failover.random.order a per nameservice configuration
Date Tue, 05 Jun 2018 22:11:00 GMT

     [ https://issues.apache.org/jira/browse/HDFS-13653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Ekanth Sethuramalingam updated HDFS-13653:
    Attachment: HDFS-13653.005.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
> 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

To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org

View raw message