[
https://issues.apache.org/jira/browse/HDFS-16613?focusedWorklogId=778146&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-778146
]
ASF GitHub Bot logged work on HDFS-16613:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 03/Jun/22 15:26
Start Date: 03/Jun/22 15:26
Worklog Time Spent: 10m
Work Description: lfxy opened a new pull request, #4398:
URL: https://github.com/apache/hadoop/pull/4398
[HDFS-16613](https://issues.apache.org/jira/browse/HDFS-16613)
In a hdfs cluster with a lot of EC blocks, decommission a dn is very slow.
The reason is unlike replication blocks can be replicated from any dn which has
the same block replication, the ec block have to be replicated from the
decommissioning dn.
The configurations dfs.namenode.replication.max-streams and
dfs.namenode.replication.max-streams-hard-limit will limit the replication
speed, but increase these configurations will create risk to the whole
cluster's network. So it should add a new configuration to limit the
decommissioning dn, distinguished from the cluster wide max-streams limit.
Issue Time Tracking
-------------------
Worklog Id: (was: 778146)
Time Spent: 20m (was: 10m)
> EC: Improve performance of decommissioning dn with many ec blocks
> -----------------------------------------------------------------
>
> Key: HDFS-16613
> URL: https://issues.apache.org/jira/browse/HDFS-16613
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: ec, erasure-coding, namenode
> Affects Versions: 3.4.0
> Reporter: caozhiqiang
> Assignee: caozhiqiang
> Priority: Major
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In a hdfs cluster with a lot of EC blocks, decommission a dn is very slow.
> The reason is unlike replication blocks can be replicated from any dn which
> has the same block replication, the ec block have to be replicated from the
> decommissioning dn.
> The configurations dfs.namenode.replication.max-streams and
> dfs.namenode.replication.max-streams-hard-limit will limit the replication
> speed, but increase these configurations will create risk to the whole
> cluster's network. So it should add a new configuration to limit the
> decommissioning dn, distinguished from the cluster wide max-streams limit.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
