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/11/04 06:20:00 UTC

[jira] [Commented] (HDFS-16811) Support DecommissionBackoffMonitor parameters reconfigurable

    [ https://issues.apache.org/jira/browse/HDFS-16811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17628698#comment-17628698 ] 

ASF GitHub Bot commented on HDFS-16811:
---------------------------------------

tomscut merged PR #5068:
URL: https://github.com/apache/hadoop/pull/5068




> Support DecommissionBackoffMonitor parameters reconfigurable 
> -------------------------------------------------------------
>
>                 Key: HDFS-16811
>                 URL: https://issues.apache.org/jira/browse/HDFS-16811
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>            Reporter: Haiyang Hu
>            Assignee: Haiyang Hu
>            Priority: Major
>              Labels: pull-request-available
>
> When the Backoff monitor is enabled, decommissionBackoffMonitor Parameters to reconfigurable
> 1.the parameter dfs.namenode.decommission.backoff.monitor.pending.limit can be dynamically adjusted to determines the maximum number of blocks related to decommission and maintenance operations that can be loaded into the replication queue.
> 2.the parameter dfs.namenode.decommission.backoff.monitor.pending.blocks.per.lock can be dynamically adjusted to determines release the namenode write lock after the numbe of blocks to process when moving blocks to pendingReplication .



--
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