[
https://issues.apache.org/jira/browse/HDFS-7281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14511591#comment-14511591
]
Yongjun Zhang commented on HDFS-7281:
-------------------------------------
Thanks [~aw] and [~cnauroth] for addressing my questions in the email thread.
{quote}
What about adding new entries to jmx report? Somehow I had the impression that
if we add new entries to it, it's not considered incompatible. Often within the
same minor release, we want to add new info to jmx report instead of waiting
for a major release.
For CLI like fsck, maybe we can add a new command line option to enable the
change, and if the command line option is not enabled, don't change the output,
so we can still commit the change within the same release line?
quote}
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-4.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)
