You are viewing a plain text version of this content. The canonical link for it is here.

Posted to hdfs-issues@hadoop.apache.org by "Erik Krogen (JIRA)" <ji...@apache.org> on 2018/05/23 00:05:00 UTC

[jira] [Created] (HDFS-13602) Optimize checkOperation(WRITE) check in FSNamesystem getBlockLocations

Erik Krogen created HDFS-13602:
----------------------------------

             Summary: Optimize checkOperation(WRITE) check in FSNamesystem getBlockLocations
                 Key: HDFS-13602
                 URL: https://issues.apache.org/jira/browse/HDFS-13602
             Project: Hadoop HDFS
          Issue Type: Improvement
          Components: ha, namenode
            Reporter: Erik Krogen
            Assignee: Chao Sun


Similar to the work done in HDFS-4591 to avoid having to take a write lock before checking if an operation category is allowed, we can do the same for the write lock that is taken sometimes (when updating access time) within getBlockLocations.

This is particularly useful when using the standby read feature (HDFS-12943), as it will be the case on an observer node that the operationCategory(READ) check succeeds but the operationCategory(WRITE) check fails. It would be ideal to fail this check _before_ acquiring the write lock.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org