[ 
https://issues.apache.org/jira/browse/HDFS-13602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16494197#comment-16494197
 ] 

Chao Sun commented on HDFS-13602:
---------------------------------

Thanks [~shv]. Uploaded patch v1 to address the comments.

> 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
>            Priority: Major
>         Attachments: HDFS-13602.000.patch, HDFS-13602.001.patch
>
>
> 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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org

Reply via email to