[
https://issues.apache.org/jira/browse/HDFS-16974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xiaoqiao He resolved HDFS-16974.
--------------------------------
Fix Version/s: 3.4.0
Hadoop Flags: Reviewed
Resolution: Fixed
> Consider volumes average load of each DataNode when choosing target.
> --------------------------------------------------------------------
>
> Key: HDFS-16974
> URL: https://issues.apache.org/jira/browse/HDFS-16974
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: Shuyan Zhang
> Assignee: Shuyan Zhang
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.4.0
>
>
> The current target choosing policy only considers the load of the entire
> datanode. If both DN1 and DN2 have an `xceiverCount` of 100, but DN1 has 10
> volumes to write to and DN2 only has 1, then the pressure on DN2 is actually
> much greater than that on DN1. This patch has added a configuration that
> allows us to avoid nodes with too much pressure on a single volume when
> choosing targets, so as to avoid overloading datanodes with few volumes or
> slowing down writes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org
