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 "Eli Collins (JIRA)" <ji...@apache.org> on 2012/09/14 08:06:07 UTC

[jira] [Created] (HDFS-3937) The BlockManager should not use the FSN lock

Eli Collins created HDFS-3937:
---------------------------------

             Summary: The BlockManager should not use the FSN lock
                 Key: HDFS-3937
                 URL: https://issues.apache.org/jira/browse/HDFS-3937
             Project: Hadoop HDFS
          Issue Type: Sub-task
          Components: name-node
            Reporter: Eli Collins


Like HDFS-2206 but for the BM. The BM currently calls into the FSN to acquire it's write lock, it looks like this is only needed for synchronization of it's local structures, in which case it can have it's own RW lock. This helps us further decouple block and namespace management, and also avoids scenarios like HDFS-3936 where the FSN holds the lock and calls into BM which may be blocked trying to acquire the FSN lock.

Per Todd's comment in HDFS-2206 we should do this as part of revisiting NN locking (HDFS-2184) vs just a local change.   

--
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