[
https://issues.apache.org/jira/browse/HDFS-3573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon updated HDFS-3573:
------------------------------
Resolution: Fixed
Fix Version/s: 3.0.0
Hadoop Flags: Reviewed
Status: Resolved (was: Patch Available)
> 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
>
> Attachments: 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
