[ https://issues.apache.org/jira/browse/HDFS-16093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17528889#comment-17528889 ]
Renukaprasad C commented on HDFS-16093: --------------------------------------- [~Daniel Ma] Thanks for reporting the issue. Thanks [~hexiaoqiao] [~sodonnell] [~tomscut] for review & feedback. I do agree with [~hexiaoqiao] / [~tomscut] / [~sodonnell] , instead of excluding the Decommissioning (Decommissioned), this can be placed last. And read will be success with other normal DNs. Are you still working on this solution? > 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 > Assignee: 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.20.7#820007) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org