hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chao Sun (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-13602) Optimize checkOperation(WRITE) check in FSNamesystem getBlockLocations
Date Thu, 24 May 2018 21:18:00 GMT

     [ https://issues.apache.org/jira/browse/HDFS-13602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Chao Sun updated HDFS-13602:
    Attachment: HDFS-13602.000.patch

> 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
> 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-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org

View raw message