[
https://issues.apache.org/jira/browse/HDFS-15764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17274273#comment-17274273
]
Xiaoqiao He commented on HDFS-15764:
------------------------------------
Thanks [~hadoop_yangyun], [~ayushtkn] and [~elgoiri] discuss this improvement
here. I agree that it will postpone awareness about deleted or corrupt blocks
for NN rely on FBR. However I am concerned about if there will be RPC request
flood (blockReceivedAndDeleted) to NN when one disk failed before found by
FailVolumeScanner.
A. Send one RPC request to NN (blockReport)
B. Send many RPC request NN (blockReceivedAndDeleted), the amount is related
number of blocks located at the failed volume.
Please correct me if I don't understand correctly. Thanks.
> Notify Namenode missing or new block on disk as soon as possible
> ----------------------------------------------------------------
>
> Key: HDFS-15764
> URL: https://issues.apache.org/jira/browse/HDFS-15764
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: datanode
> Reporter: Yang Yun
> Assignee: Yang Yun
> Priority: Minor
> Attachments: HDFS-15764.001.patch, HDFS-15764.002.patch
>
>
> When a bock file is deleted on disk or copied back to the disk, the
> DirectoryScanner can find the change, but the namenode know the change only
> untill the next full report. And in big cluster the period of full report is
> set to long time invterval.
> Call notifyNamenodeDeletedBlock if block files are deleted and call
> notifyNamenodeReceivedBlock if the block files is found agian. So the
> Incremental block report can send the change to namenode in next heartbeat.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
