hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-3573) Supply NamespaceInfo when instantiating JournalManagers
Date Wed, 27 Jun 2012 02:08:45 GMT

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

Hadoop QA commented on HDFS-3573:
---------------------------------

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12533581/hdfs-3573.txt
  against trunk revision .

    +1 @author.  The patch does not contain any @author tags.

    -1 tests included.  The patch doesn't appear to include any new or modified tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    -1 javac.  The patch appears to cause the build to fail.

Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/2706//console

This message is automatically generated.
                
> 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
>         Attachments: 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message