hadoop-hdfs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Erik Krogen (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HDFS-13602) Optimize checkOperation(WRITE) check in FSNamesystem getBlockLocations
Date Wed, 23 May 2018 00:05:00 GMT
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

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

View raw message