hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "GAO Rui (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-7537) fsck is confusing when dfs.namenode.replication.min > 1 && missing replicas && NN restart
Date Thu, 26 Feb 2015 01:41:05 GMT

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

GAO Rui commented on HDFS-7537:
-------------------------------

I have attached two screen shots image: "Screen Shot 2015-02-26 at 10.27.46" and "Screen Shot
2015-02-26 at 10.30.35".

The first image shows that "Hadoop QA" ran the unit tests and encountered test failures in
"TestLeaseRecovery2.java". But, I have ran the same unit tests in IntelliJ IDEA,  the second
image shows that all the tests are passed. I have no idea how could that happen, I think changes
in fsck should not influent  "TestLeaseRecovery2.java" tests, right?

> fsck is confusing when dfs.namenode.replication.min > 1 && missing replicas
&& NN restart
> -----------------------------------------------------------------------------------------
>
>                 Key: HDFS-7537
>                 URL: https://issues.apache.org/jira/browse/HDFS-7537
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: namenode
>            Reporter: Allen Wittenauer
>            Assignee: GAO Rui
>         Attachments: HDFS-7537.1.patch, HDFS-7537.2.patch, Screen Shot 2015-02-26 at
10.27.46.png, Screen Shot 2015-02-26 at 10.30.35.png, dfs-min-2-fsck.png, dfs-min-2.png
>
>
> If minimum replication is set to 2 or higher and some of those replicas are missing and
the namenode restarts, it isn't always obvious that the missing replicas are the reason why
the namenode isn't leaving safemode.  We should improve the output of fsck and the web UI
to make it obvious that the missing blocks are from unmet replicas vs. completely/totally
missing.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message