[
https://issues.apache.org/jira/browse/HDFS-16498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17503966#comment-17503966
]
JiangHua Zhu commented on HDFS-16498:
-------------------------------------
This seems to be a robustness issue with the NameNode.
A normal BlockReport workflow:
1. The DataNode registers itself with the NameNode.
2. The DataNode sends a reporting request to the NameNode.
3.NameNode starts working for BlockReport.
It looks like this happens when the NameNode and DataNode restart at the same
time.
When this happens, should the log prompt become warn or Info more appropriate.
This is just my thought.
!screenshot-1.png!
> Fix NPE for checkBlockReportLease
> ---------------------------------
>
> Key: HDFS-16498
> URL: https://issues.apache.org/jira/browse/HDFS-16498
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: tomscut
> Assignee: tomscut
> Priority: Major
> Labels: pull-request-available
> Attachments: image-2022-03-09-20-35-22-028.png, screenshot-1.png
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> During the restart of Namenode, a Datanode is not registered, but this
> Datanode triggers FBR, which causes NPE.
> !image-2022-03-09-20-35-22-028.png|width=871,height=158!
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
