[
https://issues.apache.org/jira/browse/HDFS-15422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kihwal Lee updated HDFS-15422:
------------------------------
Description:
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
was:
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.
> 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
> Priority: Critical
>
> 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
