You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-dev@hadoop.apache.org by "Uma Maheswara Rao G (JIRA)" <ji...@apache.org> on 2013/12/13 10:14:07 UTC
[jira] [Created] (HDFS-5665) Remove the unnecessary writeLock while
initializing CacheManager in FsNameSystem Ctor
Uma Maheswara Rao G created HDFS-5665:
-----------------------------------------
Summary: 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: 2.2.0, 3.0.0
Reporter: Uma Maheswara Rao G
Assignee: Uma Maheswara Rao G
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)