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

Posted to common-issues@hadoop.apache.org by "Xiaoyu Yao (Jira)" <ji...@apache.org> on 2020/08/14 23:10:00 UTC

[jira] [Updated] (HADOOP-17208) LoadBalanceKMSClientProvider#deleteKey should invalidateCache via all KMSClientProvider instances

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

Xiaoyu Yao updated HADOOP-17208:
--------------------------------
    Summary: LoadBalanceKMSClientProvider#deleteKey should invalidateCache via all KMSClientProvider instances  (was: LoadBalanceKMSClientProvider#deleteKey should invalidateCache for all the KMSClientProvider instances)

> LoadBalanceKMSClientProvider#deleteKey should invalidateCache via all KMSClientProvider instances
> -------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-17208
>                 URL: https://issues.apache.org/jira/browse/HADOOP-17208
>             Project: Hadoop Common
>          Issue Type: Improvement
>    Affects Versions: 2.8.4
>            Reporter: Xiaoyu Yao
>            Assignee: Xiaoyu Yao
>            Priority: Major
>
> Without invalidateCache, the deleted key may still exists in the servers' key cache (CachingKeyProvider in KMSWebApp.java)  where the delete key was not hit. Client may still be able to access encrypted files by specifying to connect to KMS instances with a cached version of the deleted key before the cache entry (10 min by default) expired. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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