[
https://issues.apache.org/jira/browse/HDFS-7281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14501145#comment-14501145
]
Yongjun Zhang commented on HDFS-7281:
-------------------------------------
Hi [~mingma],
Thanks for the updated patch, it looks good to me.
I agree that
{quote}
if some tools expect "Corrupt blocks" line follows right after "Average block
replication" line, that could break
{quote}
However, personally I think that the tool is too vulnerable if it counts on the
exact sequence of the fsck report. I know that adding one entry in the jmx
report is not considered incompatible.
We can certainly add a description to the release notes about the newly added
line.
Thanks.
> Missing block is marked as corrupted block
> ------------------------------------------
>
> Key: HDFS-7281
> URL: https://issues.apache.org/jira/browse/HDFS-7281
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Ming Ma
> Assignee: Ming Ma
> Labels: supportability
> Attachments: HDFS-7281-2.patch, HDFS-7281-3.patch, HDFS-7281.patch
>
>
> In the situation where the block lost all its replicas, fsck shows the block
> is missing as well as corrupted. Perhaps it is better not to mark the block
> corrupted in this case. The reason it is marked as corrupted is
> numCorruptNodes == numNodes == 0 in the following code.
> {noformat}
> BlockManager
> final boolean isCorrupt = numCorruptNodes == numNodes;
> {noformat}
> Would like to clarify if it is the intent to mark missing block as corrupted
> or it is just a bug.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
