[
https://issues.apache.org/jira/browse/HDFS-4288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13548938#comment-13548938
]
Suresh Srinivas commented on HDFS-4288:
---------------------------------------
bq. Better yet, the logic would be to (seqNum == 0 || seqNum != lastSeqNum).
However this requires writable/RPC changes on 23, and protobuf changes on
trunk/2 and trying to ensure backwards compatibility with an optional protobuf
field, etc. Would you be ok if I filed another jira?
Separate jira should be fine. We may want to mark this jira as 0.23 only.
> NN accepts incremental BR as IBR in safemode
> --------------------------------------------
>
> Key: HDFS-4288
> URL: https://issues.apache.org/jira/browse/HDFS-4288
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
> Affects Versions: 0.23.0, 2.0.0-alpha, 3.0.0
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Priority: Critical
> Attachments: HDFS-4288.branch-23.patch
>
>
> If a DN is ready to send an incremental BR and the NN goes down, the DN will
> repeatedly try to reconnect. The NN will then process the DN's incremental
> BR as an initial BR. The NN now thinks the DN has only a few blocks, and
> will ignore all subsequent BRs from that DN until out of safemode -- which it
> may never do because of all the "missing" blocks on the affected DNs.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
