hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yongjun Zhang (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-7281) Missing block is marked as corrupted block
Date Fri, 01 May 2015 16:00:12 GMT

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

Yongjun Zhang updated HDFS-7281:
--------------------------------
          Component/s: HDFS
     Target Version/s: 3.0.0
    Affects Version/s: 3.0.0
        Fix Version/s: 3.0.0
         Hadoop Flags: Incompatible change,Reviewed  (was: Incompatible change)

> 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
>          Components: HDFS
>    Affects Versions: 3.0.0
>            Reporter: Ming Ma
>            Assignee: Ming Ma
>              Labels: supportability
>             Fix For: 3.0.0
>
>         Attachments: HDFS-7281-2.patch, HDFS-7281-3.patch, HDFS-7281-4.patch, HDFS-7281-5.patch,
HDFS-7281-6.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)

Mime
View raw message