[
https://issues.apache.org/jira/browse/HDFS-17210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17775598#comment-17775598
]
ASF GitHub Bot commented on HDFS-17210:
---------------------------------------
zhangshuyan0 commented on PR #6113:
URL: https://github.com/apache/hadoop/pull/6113#issuecomment-1763983788
> Thanks @zhangshuyan0 for your notice, It seems the variable name a bit
long (over 100), so the checkstyle always complains. do you have better ideas
for this case? <img alt="image" width="973"
src="https://user-images.githubusercontent.com/46367746/275396177-cb0e894b-208b-4088-b798-784512a0d16c.png">
I just didn't notice that the reason was that the variable name was too
long. That's it then.
> 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]