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 "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2022/08/09 15:57:00 UTC
[jira] [Commented] (HDFS-16663) Allow block reconstruction pending timeout refreshable to increase decommission performance
[ https://issues.apache.org/jira/browse/HDFS-16663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17577497#comment-17577497 ]
ASF GitHub Bot commented on HDFS-16663:
---------------------------------------
lfxy commented on PR #4567:
URL: https://github.com/apache/hadoop/pull/4567#issuecomment-1209571853
@jojochuang Could you help to review and merge this patch if you have time? Thank you.
> Allow block reconstruction pending timeout refreshable to increase decommission performance
> -------------------------------------------------------------------------------------------
>
> Key: HDFS-16663
> URL: https://issues.apache.org/jira/browse/HDFS-16663
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: ec, namenode
> Affects Versions: 3.4.0
> Reporter: caozhiqiang
> Assignee: caozhiqiang
> Priority: Major
> Labels: pull-request-available
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> In HDFS-16613, increase the value of dfs.namenode.replication.max-streams-hard-limit would maximize the IO performance of the decommissioning DN, which has a lot of EC blocks. Besides this, we also need to decrease the value of dfs.namenode.reconstruction.pending.timeout-sec, default is 5 minutes, to shorten the interval time for checking pendingReconstructions. Or the decommissioning node would be idle to wait for copy tasks in most of this 5 minutes.
> In decommission progress, we may need to reconfigure these 2 parameters several times. In HDFS-14560, the dfs.namenode.replication.max-streams-hard-limit can already be reconfigured dynamically without namenode restart. And the dfs.namenode.reconstruction.pending.timeout-sec parameter also need to be reconfigured dynamically.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org