hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-7993) Provide each Replica details in fsck
Date Tue, 21 Apr 2015 10:44:01 GMT

    [ https://issues.apache.org/jira/browse/HDFS-7993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14504752#comment-14504752
] 

Hudson commented on HDFS-7993:
------------------------------

FAILURE: Integrated in Hadoop-Yarn-trunk #904 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk/904/])
HDFS-7993. Provide each Replica details in fsck (Contributed by J.Andreina) (vinayakumarb:
rev 8ddbb8dd433862509bd9b222dddafe2c3a74778a)
* hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestFsck.java
* hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/blockmanagement/DatanodeStorageInfo.java
* hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/NamenodeFsck.java
* hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/tools/DFSck.java


> Provide each Replica details in fsck
> ------------------------------------
>
>                 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
>             Fix For: 2.8.0
>
>         Attachments: HDFS-7993.1.patch, HDFS-7993.2.patch, HDFS-7993.3.patch, HDFS-7993.4.patch,
HDFS-7993.5.patch, HDFS-7993.6.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)

Mime
View raw message