[
https://issues.apache.org/jira/browse/HDFS-14554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16940646#comment-16940646
]
Xiaoqiao He commented on HDFS-14554:
------------------------------------
Thanks [~lindongdong] for your comments. This ticket is not valid. I just
suggest to try lifeline feature or update safemode checking
mechanism/HDFS-14559 is one demo implementation or turn off safemode auto leave
when namenode startup if you also meet bottleneck about namenode restart. My
own opinion FYI.
> Avoid to process duplicate blockreport of datanode when namenode in startup
> safemode
> ------------------------------------------------------------------------------------
>
> Key: HDFS-14554
> URL: https://issues.apache.org/jira/browse/HDFS-14554
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: namenode
> Reporter: Xiaoqiao He
> Assignee: Xiaoqiao He
> Priority: Major
> Attachments: HDFS-14554.001.patch
>
>
> When NameNode restart and enter stage of startup safemode, load of NameNode
> could be very high since blockreport request storm from datanodes together.
> Sometimes datanode may request blockreport times because NameNode doesn't
> return in time and DataNode meet timeoutexception then retry, Thus it
> sharpens load of NameNode.
> So we should check and filter duplicate blockreport request from one
> datannode and reduce load of Namenode.
--
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
