[
https://issues.apache.org/jira/browse/HDFS-16514?focusedWorklogId=757291&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-757291
]
ASF GitHub Bot logged work on HDFS-16514:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 15/Apr/22 04:20
Start Date: 15/Apr/22 04:20
Worklog Time Spent: 10m
Work Description: liubingxing commented on PR #4088:
URL: https://github.com/apache/hadoop/pull/4088#issuecomment-1099836851
@tasanuma Please take a look at this. Thanks a lot.
Issue Time Tracking
-------------------
Worklog Id: (was: 757291)
Time Spent: 1.5h (was: 1h 20m)
> Reduce the failover sleep time if multiple namenode are configured
> ------------------------------------------------------------------
>
> Key: HDFS-16514
> URL: https://issues.apache.org/jira/browse/HDFS-16514
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: qinyuren
> Priority: Major
> Labels: pull-request-available
> Attachments: image-2022-03-21-18-11-37-191.png
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> Recently, we used the [Standby Read] feature in our test cluster, and
> deployed 4 namenode as follow:
> node1 -> active nn
> node2 -> standby nn
> node3 -> observer nn
> node3 -> observer nn
> If we set ’dfs.client.failover.random.order=true‘, the client may failover
> twice and wait a long time to send msync to active namenode.
> !image-2022-03-21-18-11-37-191.png|width=698,height=169!
> I think we can reduce the sleep time of the first several failover based on
> the number of namenode
> For example, if 4 namenode are configured, the sleep time of first three
> failover operations is set to zero.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
