hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zhe Zhang (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-10458) getFileEncryptionInfo should return quickly for non-encrypted cluster
Date Mon, 06 Jun 2016 18:43:21 GMT

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

Zhe Zhang updated HDFS-10458:
    Attachment: HDFS-10458.05.patch

Updating patch to address unit test failures. Thanks [~shv] for the review.

> getFileEncryptionInfo should return quickly for non-encrypted cluster
> ---------------------------------------------------------------------
>                 Key: HDFS-10458
>                 URL: https://issues.apache.org/jira/browse/HDFS-10458
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: encryption, namenode
>    Affects Versions: 2.6.0
>            Reporter: Zhe Zhang
>            Assignee: Zhe Zhang
>         Attachments: HDFS-10458.00.patch, HDFS-10458.03.patch, HDFS-10458.04.patch, HDFS-10458.05.patch,
HDFSA-10458.01.patch, HDFSA-10458.02.patch
> {{FSDirectory#getFileEncryptionInfo}} always acquires {{readLock}} and checks if the
path belongs to an EZ. For a busy system with potentially many listing operations, this could
cause locking contention.
> I think we should add a call {{EncryptionZoneManager#hasEncryptionZone()}} to return
whether the system has any EZ. If no EZ at all, {{getFileEncryptionInfo}} should return null
without {{readLock}}.
> If {{hasEncryptionZone}} is only used in the above scenario, maybe itself doesn't need
a {{readLock}} -- if the system doesn't have any EZ when {{getFileEncryptionInfo}} is called
on a path, it means the path cannot be encrypted.

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