[
https://issues.apache.org/jira/browse/HDFS-10899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xiao Chen updated HDFS-10899:
-----------------------------
Attachment: HDFS-10899.14.patch
Thanks again [~daryn] for the guidelines about general benchmarking.
I have run some numbers, proving the throttler to work. Shared a result
[doc|https://docs.google.com/document/d/18mP2hbBHSoVriBgtArQkOLSPdwpxo5lk3MQwYz0s7y8/edit#heading=h.xh5gibeh09wp].
Unfortunately for the time being I don't have a beefy enough machine to stress
the NN to reach the ops/sec you described, and only have a
[gce|https://cloud.google.com/compute/pricing] instance. Therefore as shown in
the doc, the stress is bottlenecked on CPU, instead of the read/write lock.
Some highlights from the doc which I think shows the throttling taking effect:
- Throttle ratio 0.1, without stress (only re-encryption), we see host CPU
dropped to be steadily < 50%.
- Without throttling, throughput during re-encryption is only ~ 65% of baseline.
- With throttle ratio 0.1, ~ 75%
- With an extreme throttle ratio of 0.001, ~90%
I'll look into why 0.001 doesn't provide a 99% throughput. But otherwise ready
for review.
Patch 14 is attached, based on trunk on top of HADOOP-14705's latest patch.
> Add functionality to re-encrypt EDEKs
> -------------------------------------
>
> Key: HDFS-10899
> URL: https://issues.apache.org/jira/browse/HDFS-10899
> Project: Hadoop HDFS
> Issue Type: New Feature
> Components: encryption, kms
> Reporter: Xiao Chen
> Assignee: Xiao Chen
> Attachments: editsStored, HDFS-10899.01.patch, HDFS-10899.02.patch,
> HDFS-10899.03.patch, HDFS-10899.04.patch, HDFS-10899.05.patch,
> HDFS-10899.06.patch, HDFS-10899.07.patch, HDFS-10899.08.patch,
> HDFS-10899.09.patch, HDFS-10899.10.patch, HDFS-10899.10.wip.patch,
> HDFS-10899.11.patch, HDFS-10899.12.patch, HDFS-10899.13.patch,
> HDFS-10899.14.patch, HDFS-10899.wip.2.patch, HDFS-10899.wip.patch, Re-encrypt
> edek design doc.pdf, Re-encrypt edek design doc V2.pdf
>
>
> Currently when an encryption zone (EZ) key is rotated, it only takes effect
> on new EDEKs. We should provide a way to re-encrypt EDEKs after the EZ key
> rotation, for improved security.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
