[
https://issues.apache.org/jira/browse/HADOOP-14705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16130712#comment-16130712
]
Xiao Chen commented on HADOOP-14705:
------------------------------------
bq. It is based on HADOOP-14779, and optimizes reencryptEncryptedKeys to use
the same codec (and en/de-cryptor), and only getCurrentKey once from the key
name.
Thanks for looking. As
[noted|https://issues.apache.org/jira/browse/HADOOP-14705?focusedCommentId=16129130&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16129130],
could you please apply HADOOP-14779, then patch 5 here? Only reason to
separate out HADOOP-14779 is for cleanness.
> Add batched reencryptEncryptedKey interface to KMS
> --------------------------------------------------
>
> Key: HADOOP-14705
> URL: https://issues.apache.org/jira/browse/HADOOP-14705
> Project: Hadoop Common
> Issue Type: Improvement
> Components: kms
> Reporter: Xiao Chen
> Assignee: Xiao Chen
> Attachments: HADOOP-14705.01.patch, HADOOP-14705.02.patch,
> HADOOP-14705.03.patch, HADOOP-14705.04.patch, HADOOP-14705.05.patch
>
>
> HADOOP-13827 already enabled the KMS to re-encrypt a {{EncryptedKeyVersion}}.
> As the performance results of HDFS-10899 turns out, communication overhead
> with the KMS occupies the majority of the time. So this jira proposes to add
> a batched interface to re-encrypt multiple EDEKs in 1 call.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]