[
https://issues.apache.org/jira/browse/HDFS-3573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13487789#comment-13487789
]
Hudson commented on HDFS-3573:
------------------------------
Integrated in Hadoop-Mapreduce-trunk #1242 (See
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1242/])
Moved HDFS-3573 entry in CHANGES.txt from trunk to 2.0.3-alpha section
(Revision 1403740)
Result = FAILURE
umamahesh :
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1403740
Files :
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
> 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
