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 "Alejandro Abdelnur (JIRA)" <ji...@apache.org> on 2014/06/26 22:47:25 UTC

[jira] [Comment Edited] (HADOOP-10750) KMSKeyProviderCache should be in hadoop-common

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

Alejandro Abdelnur edited comment on HADOOP-10750 at 6/26/14 8:45 PM:
----------------------------------------------------------------------

On #1, correct. Plus both expiration times should be configurable.

On #2, KMS is an obvious candidate. KeyProvider implementations that want to manage their own caching as well. And any service using KeyProviders, i.e. Oozie, NN, httpfs, Knox, etc. Even AMs of Yarn Jobs could benefit from it.


was (Author: tucu00):
On #1, correct. Plus both expiration times should be configurable.

On #2, KMS is an obvious candidate. KeyProvider implementations that want to manage their own caching as well. And any service using KeyProviders, i.e. Oozie, NN, httpfs, Knox, etc. Even AMs of Yarn Jobs could benefit for it.

> KMSKeyProviderCache should be in hadoop-common
> ----------------------------------------------
>
>                 Key: HADOOP-10750
>                 URL: https://issues.apache.org/jira/browse/HADOOP-10750
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: security
>    Affects Versions: 3.0.0
>            Reporter: Alejandro Abdelnur
>            Assignee: Alejandro Abdelnur
>
> KMS has {{KMSCacheKeyProvider}}, this class should be available in hadoop-common for users of  {{KeyProvider}} instances to wrap them and avoid several, potentially expensive, key retrievals.



--
This message was sent by Atlassian JIRA
(v6.2#6252)