[
https://issues.apache.org/jira/browse/HDFS-5665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Wang updated HDFS-5665:
------------------------------
Resolution: Fixed
Fix Version/s: 3.0.0
Hadoop Flags: Reviewed
Status: Resolved (was: Patch Available)
Committed to trunk, thanks again Uma.
> Remove the unnecessary writeLock while initializing CacheManager in
> FsNameSystem Ctor
> -------------------------------------------------------------------------------------
>
> Key: HDFS-5665
> URL: https://issues.apache.org/jira/browse/HDFS-5665
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: namenode
> Affects Versions: 3.0.0, 2.2.0
> Reporter: Uma Maheswara Rao G
> Assignee: Uma Maheswara Rao G
> Fix For: 3.0.0
>
> Attachments: HDFS-5665.patch
>
>
> I just saw the below piece of code in Fsnamesystem ctor.
> {code}
> writeLock();
> try {
> this.cacheManager = new CacheManager(this, conf, blockManager);
> } finally {
> writeUnlock();
> }
> {code}
> It seems unnecessary to keep writeLock here. I am not sure if there is a
> clear reason to keep the lock.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
