[
https://issues.apache.org/jira/browse/HDFS-2223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099302#comment-13099302
]
Todd Lipcon commented on HDFS-2223:
-----------------------------------
How about this: we can keep getNamespaceInfo with the readlock, and delegate
inside the lock to getNamespaceInfoInternal(). From within saveNamespace, we
can directly call the getNamespaceInfoInternal method, since we know that the
outer coordinating thread of saveNamespace is holding the lock "on our behalf".
> Untangle depencencies between NN components
> -------------------------------------------
>
> Key: HDFS-2223
> URL: https://issues.apache.org/jira/browse/HDFS-2223
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: name-node
> Affects Versions: 0.23.0
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Attachments: hdfs-2223-1.txt, hdfs-2223-2.txt, hdfs-2223-3.txt,
> hdfs-2223-4.txt, hdfs-2223-5.txt, hdfs-2223-6.txt, hdfs-2223-7.txt,
> hdfs-2223-8.txt, hdfs-2223-9.txt
>
>
> Working in the NN a lot for HA (HDFS-1623) I've come across a number of
> situations where the tangled dependencies between NN components has been
> problematic for adding new features and for testability. It would be good to
> untangle some of these and clarify what the distinction is between the
> different components: NameNode, FSNamesystem, FSDirectory, FSImage,
> NNStorage, and FSEditLog
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
