hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uma Maheswara Rao G (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-3573) Supply NamespaceInfo when instantiating JournalManagers
Date Tue, 30 Oct 2012 01:12:12 GMT

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

Uma Maheswara Rao G commented on HDFS-3573:
-------------------------------------------

I have just committed this to branch-2.
Committed revision 1403594.
                
> Supply NamespaceInfo when instantiating JournalManagers
> -------------------------------------------------------
>
>                 Key: HDFS-3573
>                 URL: https://issues.apache.org/jira/browse/HDFS-3573
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: name-node
>    Affects Versions: 3.0.0
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>            Priority: Minor
>             Fix For: 3.0.0, 2.0.3-alpha
>
>         Attachments: 0001-HDFS-3573-for-branch-2.patch, hdfs-3573.txt, hdfs-3573.txt,
hdfs-3573.txt, hdfs-3573.txt
>
>
> Currently, the JournalManagers are instantiated before the NamespaceInfo is loaded from
local storage directories. This is problematic since the JM may want to verify that the storage
info associated with the journal matches the NN which is starting up (eg to prevent an operator
accidentally configuring two clusters against the same remote journal storage). This JIRA
rejiggers the initialization sequence so that the JMs receive NamespaceInfo as a constructor
argument.

--
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