hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wei-Chiu Chuang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-14705) Add batched reencryptEncryptedKey interface to KMS
Date Thu, 17 Aug 2017 21:33:02 GMT

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

Wei-Chiu Chuang commented on HADOOP-14705:

Thanks for the new patch, Xiao.

Looking at rev 007, I feel like adding an artificial, hard-coded limit of size of payload
is not the best approach.
Preconditions.checkArgument(jsonPayload.size() <= MAX_NUM_PER_BATCH,
	          "jsonPayload too many objects");
I would actually prefer to log a warning if the size exceed a certain limit, than rejecting
it right away.

After adding this interface, does it deprecate the old reencrypt interface added in HADOOP-13827?

> 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-14705.06.patch, HADOOP-14705.07.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

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

View raw message