[HDFS-13653] Make dfs.client.failover.random.order a per nameservice configuration - ASF JIRA

XML

Word

Printable

JSON

Details

Type: Improvement
Status: Resolved
Priority: Major
Resolution: Fixed
Affects Version/s: None
Fix Version/s: 2.10.0, 3.2.0, 3.1.1, 2.9.2, 3.0.4
Component/s: federation
Labels:
None

Hadoop Flags:

Reviewed

Description

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.

Attachments

- Sort By Name
- Sort By Date
- Ascending
- Descending

HDFS-13653.001.patch
04/Jun/18 21:53
2 kB
Ekanth Sethuramalingam
HDFS-13653.002.patch
05/Jun/18 06:51
3 kB
Ekanth Sethuramalingam
HDFS-13653.003.patch
05/Jun/18 07:27
3 kB
Ekanth Sethuramalingam
HDFS-13653.004.patch
05/Jun/18 21:42
12 kB
Ekanth Sethuramalingam
HDFS-13653.005.patch
05/Jun/18 22:10
12 kB
Ekanth Sethuramalingam
HDFS-13653.006.patch
06/Jun/18 02:37
13 kB
Ekanth Sethuramalingam
HDFS-13653.007.patch
06/Jun/18 16:20
13 kB
Ekanth Sethuramalingam
HDFS-13653.008.patch
07/Jun/18 05:26
14 kB
Ekanth Sethuramalingam
HDFS-13653.009.branch-2.patch
11/Jun/18 20:33
14 kB
Ekanth Sethuramalingam
HDFS-13653.009.patch
07/Jun/18 21:07
14 kB
Ekanth Sethuramalingam
HDFS-13653.010.patch
08/Jun/18 01:06
14 kB
Ekanth Sethuramalingam

Issue Links

is related to

HDFS-6648 Order of namenodes in ConfiguredFailoverProxyProvider is undefined

Resolved

HDFS-12615 Router-based HDFS federation phase 2

Resolved

Activity

People

Assignee:: Ekanth Sethuramalingam

Reporter:: Ekanth Sethuramalingam

Votes:: 0 Vote for this issue

Watchers:: 5 Start watching this issue

Dates

Created:: 04/Jun/18 05:06

Updated:: 11/Jun/18 20:48

Resolved:: 11/Jun/18 18:20