hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron T. Myers (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-4279) NameNode does not initialize generic conf keys when started with -recover
Date Fri, 07 Dec 2012 23:55:21 GMT

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

Aaron T. Myers updated HDFS-4279:
---------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0.3-alpha
     Hadoop Flags: Reviewed
           Status: Resolved  (was: Patch Available)

Thanks a lot for the patch and the testing, Colin. I've just committed this to trunk and branch-2.
                
> 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