[
https://issues.apache.org/jira/browse/HDFS-8872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rushabh S Shah updated HDFS-8872:
---------------------------------
Description:
Namenode ui and metasave will not report a block as missing if the only replica
is on decommissioning/decomissioned node while fsck will show it as MISSING.
Since decommissioned node can be formatted/removed anytime, we can actually
lose the block.
Its better to alert on namenode ui if the only copy is on
decomissioned/decommissioning node.
was:
Namenode ui and metasave will not report a block as missing if the only replica
is on decommissioning/decomissioned node where fsck will show it as MISSING.
Since decommissioned node can be formatted/removed anytime, we can actually
lose the block.
Its better to alert on namenode ui if the only copy is on
decomissioned/decommissioning node.
> Reporting of missing blocks is different in fsck and namenode ui/metasave
> -------------------------------------------------------------------------
>
> Key: HDFS-8872
> URL: https://issues.apache.org/jira/browse/HDFS-8872
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 2.6.0
> Reporter: Rushabh S Shah
> Assignee: Rushabh S Shah
> Fix For: 2.7.2
>
>
> Namenode ui and metasave will not report a block as missing if the only
> replica is on decommissioning/decomissioned node while fsck will show it as
> MISSING.
> Since decommissioned node can be formatted/removed anytime, we can actually
> lose the block.
> Its better to alert on namenode ui if the only copy is on
> decomissioned/decommissioning node.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
