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-4279) NameNode does not initialize generic conf keys when started with -recover
Date Sat, 08 Dec 2012 13:09:22 GMT

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

Hudson commented on HDFS-4279:
------------------------------

Integrated in Hadoop-Hdfs-trunk #1248 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/1248/])
    HDFS-4279. NameNode does not initialize generic conf keys when started with -recover.
Contributed by Colin Patrick McCabe. (Revision 1418559)

     Result = FAILURE
atm : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1418559
Files : 
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/NameNode.java
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestNameNodeRecovery.java

                
> NameNode does not initialize generic conf keys when started with -recover
> -------------------------------------------------------------------------
>
>                 Key: HDFS-4279
>                 URL: https://issues.apache.org/jira/browse/HDFS-4279
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: namenode
>    Affects Versions: 2.0.3-alpha
>            Reporter: Colin Patrick McCabe
>            Assignee: Colin Patrick McCabe
>            Priority: Minor
>             Fix For: 2.0.3-alpha
>
>         Attachments: HDFS-3236.002.patch
>
>
> This means that configurations that scope the location of the name/edits/shared edits
dirs by nameserice or namenode won't work with `hdfs namenode -recover`

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message