You are viewing a plain text version of this content. The canonical link for it is here.

Posted to hdfs-issues@hadoop.apache.org by "Zhe Zhang (JIRA)" <ji...@apache.org> on 2014/09/16 02:19:34 UTC

[jira] [Commented] (HDFS-6971) Bounded staleness of EDEK caches on the NN

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

Zhe Zhang commented on HDFS-6971:
---------------------------------

{{currentKeyCache}} in {{CachingKeyProvidet}} is already created with {{expireAfterAccess}}. Is this JIRA about another cache? Regardless, a flush function is still needed.

> 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
>
> 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
(v6.3.4#6332)