[
https://issues.apache.org/jira/browse/HADOOP-14104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rushabh S Shah updated HADOOP-14104:
------------------------------------
Attachment: HADOOP-14104-trunk-v5.patch
Hopefully the last patch for trunk. :)
[~andrew.wang] [~yzhangal]: I really appreciate your feedback.
Thanks for being extremely patient with me.
Attaching a new patch addressing your comments and fixing some checkstyle
issues.
Please review.
If this patch is good for trunk, I will then attach branch-2 and branch-2.8
patch immediately.
Test failures from previous precommit build. Both tests ran fine on my machine.
1. hadoop.security.TestKDiag: Known to be flaky. Tracked via HADOOP-14030
2. hadoop.hdfs.server.datanode.TestDataNodeVolumeFailureReporting:
This also is known to be flaky. Tried to fix via HDFS-11316, HDFS-11398. But
still flaky.
> Client should always ask namenode for kms provider path.
> --------------------------------------------------------
>
> Key: HADOOP-14104
> URL: https://issues.apache.org/jira/browse/HADOOP-14104
> Project: Hadoop Common
> Issue Type: Improvement
> Components: kms
> Reporter: Rushabh S Shah
> Assignee: Rushabh S Shah
> Attachments: HADOOP-14104-trunk.patch, HADOOP-14104-trunk-v1.patch,
> HADOOP-14104-trunk-v2.patch, HADOOP-14104-trunk-v3.patch,
> HADOOP-14104-trunk-v4.patch, HADOOP-14104-trunk-v5.patch
>
>
> According to current implementation of kms provider in client conf, there can
> only be one kms.
> In multi-cluster environment, if a client is reading encrypted data from
> multiple clusters it will only get kms token for local cluster.
> Not sure whether the target version is correct or not.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
