[
https://issues.apache.org/jira/browse/HDFS-17210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17774020#comment-17774020
]
ASF GitHub Bot commented on HDFS-17210:
---------------------------------------
Hexiaoqiao commented on code in PR #6113:
URL: https://github.com/apache/hadoop/pull/6113#discussion_r1354847751
##########
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/DFSConfigKeys.java:
##########
@@ -1240,6 +1240,12 @@ public class DFSConfigKeys extends
CommonConfigurationKeys {
public static final int
DFS_NAMENODE_AVAILABLE_SPACE_BLOCK_PLACEMENT_POLICY_BALANCED_SPACE_TOLERANCE_DEFAULT
=
5;
+ public static final String
+
DFS_NAMENODE_AVAILABLE_SPACE_BLOCK_PLACEMENT_POLICY_BALANCED_SPACE_TOLERANCE_LIMIT_KEY
=
Review Comment:
I think it is OK for me now. The root cause is name of this constant is too
long, but I also have no other choice to be better. Maybe we could care that
when name next time.
> Optimize AvailableSpaceBlockPlacementPolicy
> -------------------------------------------
>
> Key: HDFS-17210
> URL: https://issues.apache.org/jira/browse/HDFS-17210
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: hdfs
> Affects Versions: 3.3.6
> Reporter: Fei Guo
> Priority: Minor
> Labels: pull-request-available
>
> for now ,we may have many nodes usage over 85%, some nodes'usage have been
> over 90%, if we choose three nodes as nodeA-97%,nodeB-98%,nodeC-99%, actually
> i don't want nodeC(99%) be choosen, for nodeC usage is really high , even
> random chance ,nodeC will reach 100% soon, so we can directly choose the less
> usage node(nodeA) if all nodes's usage are over 95%(just a example)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
