[ https://issues.apache.org/jira/browse/HDFS-17044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17731889#comment-17731889 ]
ASF GitHub Bot commented on HDFS-17044: --------------------------------------- hfutatzhanghb commented on PR #5735: URL: https://github.com/apache/hadoop/pull/5735#issuecomment-1588580362 > @hfutatzhanghb Hi, bro thanks for your comment. yeah, modification is similar to what method BlockManager#removeBlock does. If the block is no included in the BlocksMap, when DN processed invalidating blocks , should not need to notify the Namenode. > > I will add UT try to illustrate this case. @haiyang1987 Thanks bro for replying. Got it~ > Process reported block toInvalidate logic should set the block size to NO_ACK > ----------------------------------------------------------------------------- > > Key: HDFS-17044 > URL: https://issues.apache.org/jira/browse/HDFS-17044 > Project: Hadoop HDFS > Issue Type: Improvement > Reporter: Haiyang Hu > Assignee: Haiyang Hu > Priority: Major > Labels: pull-request-available > > When NameNode processes DataNode increment or full block report, if block is > not in the blocks map, it will be added to invalidate and the replica should > be removed from the data-node, and the block size should be to set NO_ACK, > should be reduce some useless DataNode block reports. -- This message was sent by Atlassian Jira (v8.20.10#820010) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org