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-6971) Bounded staleness of EDEK caches on the NN
Date Tue, 30 Sep 2014 17:12:34 GMT

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

Zhe Zhang updated HDFS-6971:
    Attachment: HDFS-6971-20140930-v1.patch

This patch changes {{ValueQueue#keyQueues}} to use {{expireAfterWrite}} instead of {{expireAfterAccess}}.
It also adds unit tests for cache expiry.[~andrew.wang] I wonder if you have a clue:
* Why was {{expireAfterAccess}} in the initial implementation
* Why were both {{expireAfterWrite}} and {{expireAfterAccess}} used in {{CachingKeyProvider}}
({{keyVersionCache}}, {{keyMetadataCache}}, and {{currentKeyCache}})

> Bounded staleness of EDEK caches on the NN
> ------------------------------------------
>                 Key: HDFS-6971
>                 URL: https://issues.apache.org/jira/browse/HDFS-6971
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: encryption
>    Affects Versions: 2.5.0
>            Reporter: Andrew Wang
>            Assignee: Zhe Zhang
>         Attachments: HDFS-6971-20140930-v1.patch
> The EDEK cache on the NN can hold onto keys after the admin has rolled the key. It'd
be good to time-bound the caches, perhaps also providing an explicit "flush" command.

This message was sent by Atlassian JIRA

View raw message