hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-8872) Reporting of missing blocks is different in fsck and namenode ui/metasave
Date Mon, 26 Oct 2015 18:21:28 GMT

     [ https://issues.apache.org/jira/browse/HDFS-8872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Vinod Kumar Vavilapalli updated HDFS-8872:
------------------------------------------
    Target Version/s: 2.7.2
       Fix Version/s:     (was: 2.7.2)

[~shahrs87], FYI, you should use target-version for your intention. Fix-version is set at
commit time. I'm fixing this for now.

> 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
>
> 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)

Mime
View raw message