hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jim Plush (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-979) FSImage should specify which dirs are missing when refusing to come up
Date Sun, 26 Jun 2011 19:21:47 GMT

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

Jim Plush commented on HDFS-979:
--------------------------------

There seem to be several other places where a generic message like this is displayed...

------------------------------------------------------------------------
➺ Ack --java "All specified directories are not accessible"
hdfs/src/java/org/apache/hadoop/hdfs/server/datanode/BlockPoolSliceStorage.java
134:          "All specified directories are not accessible or do not exist.");

hdfs/src/java/org/apache/hadoop/hdfs/server/datanode/DataStorage.java
188:          "All specified directories are not accessible or do not exist.");

hdfs/src/java/org/apache/hadoop/hdfs/server/namenode/FSImage.java
201:          "All specified directories are not accessible or do not exist.");


> FSImage should specify which dirs are missing when refusing to come up
> ----------------------------------------------------------------------
>
>                 Key: HDFS-979
>                 URL: https://issues.apache.org/jira/browse/HDFS-979
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: name-node
>    Affects Versions: 0.22.0
>            Reporter: Steve Loughran
>            Priority: Minor
>
> When {{FSImage}} can't come up as either it has no data or edit dirs, it tells me this
> {code}
> java.io.IOException: All specified directories are not accessible or do not exist.
> {code}
> What it doesn't do is say which of the two attributes are missing. This would be beneficial
to anyone trying to track down the problem. Also, I don't think the message is correct. It's
bailing out because dataDirs.size() == 0 || editsDirs.size() == 0 , because a list is empty
-not because the dirs aren't there, as there hasn't been any validation yet.
> More useful would be
> # Explicit mention of which attributes are null
> # Declare that this is because they are not in the config

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

Mime
View raw message