[
https://issues.apache.org/jira/browse/HDFS-7281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14500844#comment-14500844
]
Yongjun Zhang commented on HDFS-7281:
-------------------------------------
HI [~lohit],
Thanks for your comments. Format-wise, Ming's change added one standalone line
of "Missing blocks" to the report. As we don't consider it incompatible when we
add new entries to jmx report, I guess we don't have to mark it as
incompatible too. Do you agree?
Hi Ming, sorry about the long delay. the patch doesn't apply anymore, would you
please bring the patch up-to-date? I'd like to push it forward. 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.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)
