[
https://issues.apache.org/jira/browse/HDFS-15422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17289872#comment-17289872
]
Stephen O'Donnell commented on HDFS-15422:
------------------------------------------
Thanks for the review [~weichiu]. I committed this to trunk and the cherry-pick
was clean down to 3.1.
I have pushed a new identical 2.10 patch to re-trigger Jenkins. If that comes
back clean I will commit there too.
> Reported IBR is partially replaced with stored info when queuing.
> -----------------------------------------------------------------
>
> Key: HDFS-15422
> URL: https://issues.apache.org/jira/browse/HDFS-15422
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
> Reporter: Kihwal Lee
> Assignee: Stephen O'Donnell
> Priority: Critical
> Fix For: 3.3.1, 3.4.0, 3.1.5, 3.2.3
>
> Attachments: HDFS-15422-branch-2.10.001.patch,
> HDFS-15422-branch-2.10.002.patch, HDFS-15422.001.patch
>
>
> When queueing an IBR (incremental block report) on a standby namenode, some
> of the reported information is being replaced with the existing stored
> information. This can lead to false block corruption.
> We had a namenode, after transitioning to active, started reporting missing
> blocks with "SIZE_MISMATCH" as corrupt reason. These were blocks that were
> appended and the sizes were actually correct on the datanodes. Upon further
> investigation, it was determined that the namenode was queueing IBRs with
> altered information.
> Although it sounds bad, I am not making it blocker
--
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
