[
https://issues.apache.org/jira/browse/HDFS-15162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17273268#comment-17273268
]
JiangHua Zhu commented on HDFS-15162:
-------------------------------------
At this time, I understand that two things should be done:
1. FBR can be used only after DN is normally connected to NN;
2. After the abnormality is removed, FBR can be done at the next fixed interval
or supplemented with the last unfinished FBR.
> Optimize frequency of regular block reports
> -------------------------------------------
>
> Key: HDFS-15162
> URL: https://issues.apache.org/jira/browse/HDFS-15162
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: Ayush Saxena
> Assignee: Ayush Saxena
> Priority: Critical
>
> Avoid sending block report at regular interval, if there is no failover,
> DiskError or any exception encountered in connecting to the Namenode.
> This JIRA intents to limit the regular block reports to be sent only in case
> of the above scenarios and during re-registration of datanode, to eliminate
> the overhead of processing BlockReports at Namenode in case of huge clusters.
> *Eg.* If a block report was sent at 0000 hours and the next was scheduled at
> 0600 hours if there is no above mentioned scenario, it will skip sending the
> BR, and schedule it to next 1200 hrs. if something of such sort happens
> between 06:- 12: it would send the BR normally.
> *NOTE*: This would be optional and can be turned off by default. Would add a
> configuration to enable this.
--
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
