Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 6 Jan 2017 23:40:59 +0000 (UTC)
From: "Andrew Wang (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12737614.1409271321000.673337.1483746059643@Atlassian.JIRA>
In-Reply-To: <JIRA.12737614.1409271321000@Atlassian.JIRA>
References: <JIRA.12737614.1409271321000@Atlassian.JIRA> <JIRA.12737614.1409271321603@arcas>
Subject: [jira] [Updated] (HDFS-6971) Bounded staleness of EDEK caches on
 the NN
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 06 Jan 2017 23:41:01 -0000


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

Andrew Wang updated HDFS-6971:
------------------------------
    Resolution: Duplicate
        Status: Resolved  (was: Patch Available)

I think we can dupe this in favor of HDFS-11210 which will flush the caches on key roll.

> 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: Improvement
>          Components: encryption
>            Reporter: Andrew Wang
>            Assignee: Zhe Zhang
>              Labels: BB2015-05-TBR
>         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
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org