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] [Updated] (HDFS-979) FSImage should specify which dirs are missing when refusing to come up
Date Sun, 26 Jun 2011 22:51:47 GMT

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

Jim Plush updated HDFS-979:
---------------------------

    Attachment: HDFS-979-take1.txt

Adding a verbose (the more verbose the more helpful?) Exception message should either the
dataDirs or the editDirs show a size of 0 in the recoverTransitionRead method. It will also
loop through the directories and if they are a file scheme, check to make sure those directories
actually do exist on disk. 

For example if the Edit dirs was showing an empty list and the directory did not exist locally
the message would be: 

"All specified directories are not accessible or do not exist. Specifically:  FSImage reports
0 NameNode edit dirs. The config value of 'dfs.namenode.edits.dir' is: file:///opt/hadoop-doesnotexist/dfs/name.
 Directory: /opt/hadoop-doesnotexist/dfs/name DOES 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
>         Attachments: HDFS-979-take1.txt
>
>
> 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