[
https://issues.apache.org/jira/browse/HDFS-7993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
J.Andreina updated HDFS-7993:
-----------------------------
Attachment: HDFS-7993.4.patch
Thanks [~mingma] and [~vinayrpet] for the review and comments.
bq.Maybe we can change the description from repl to live repl? It will address
the confusion others might have.
Agree with this point. Have updated the patch accordingly.
bq.It will be useful to show "stale block content" replica
Updated the patch to provide information whether stale replica is due to
either Stale Datanode or Stale block content.
Please review the patch.
> Incorrect descriptions in fsck when nodes are decommissioned
> ------------------------------------------------------------
>
> Key: HDFS-7993
> URL: https://issues.apache.org/jira/browse/HDFS-7993
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 2.6.0
> Reporter: Ming Ma
> Assignee: J.Andreina
> Attachments: HDFS-7993.1.patch, HDFS-7993.2.patch, HDFS-7993.3.patch,
> HDFS-7993.4.patch
>
>
> When you run fsck with "-files" or "-racks", you will get something like
> below if one of the replicas is decommissioned.
> {noformat}
> blk_x len=y repl=3 [dn1, dn2, dn3, dn4]
> {noformat}
> That is because in NamenodeFsck, the repl count comes from live replicas
> count; while the actual nodes come from LocatedBlock which include
> decommissioned nodes.
> Another issue in NamenodeFsck is BlockPlacementPolicy's verifyBlockPlacement
> verifies LocatedBlock that includes decommissioned nodes. However, it seems
> better to exclude the decommissioned nodes in the verification; just like how
> fsck excludes decommissioned nodes when it check for under replicated blocks.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
