[
https://issues.apache.org/jira/browse/HDFS-16093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17371306#comment-17371306
]
tomscut commented on HDFS-16093:
--------------------------------
IMO, abnormal nodes cannot be removed directly. Maybe sorting is a better
choice, because it makes it easier to degrade read when there are not enough
normal nodes. Just like the example [~sodonnell] gave.
> DataNodes under decommission will still be returned to the client via
> getLocatedBlocks, so the client may request decommissioning datanodes to read
> which will cause badly competation on disk IO.
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: HDFS-16093
> URL: https://issues.apache.org/jira/browse/HDFS-16093
> Project: Hadoop HDFS
> Issue Type: Improvement
> Affects Versions: 3.3.1
> Reporter: Daniel Ma
> Priority: Critical
>
> DataNodes under decommission will still be returned to the client via
> getLocatedBlocks, so the client may request decommissioning datanodes to read
> which will cause badly competation on disk IO.
> Therefore, datanodes under decommission should be removed from the return
> list of getLocatedBlocks api.
> !image-2021-06-29-10-50-44-739.png!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
