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 "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2020/08/28 23:37:00 UTC
[jira] [Work logged] (HADOOP-17208)
LoadBalanceKMSClientProvider#deleteKey should invalidateCache via all
KMSClientProvider instances
[ https://issues.apache.org/jira/browse/HADOOP-17208?focusedWorklogId=476021&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-476021 ]
ASF GitHub Bot logged work on HADOOP-17208:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 28/Aug/20 23:36
Start Date: 28/Aug/20 23:36
Worklog Time Spent: 10m
Work Description: xiaoyuyao opened a new pull request #2259:
URL: https://github.com/apache/hadoop/pull/2259
https://issues.apache.org/jira/browse/HADOOP-17208
Proposed Fix:
Send invalidCache to all KMS provider instances upon delete to ensure the server side key cache is drained upon deletion.
Also fix a NPE when invalidCache for a key that has been deleted.
How is it tested:
Tested with RangerKMS with 3 instances.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 476021)
Remaining Estimate: 0h
Time Spent: 10m
> 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
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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