[
https://issues.apache.org/jira/browse/HADOOP-14104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15949300#comment-15949300
]
Rushabh S Shah commented on HADOOP-14104:
-----------------------------------------
bq. Wonder if you have chance to look at Daryn's comments?
I was out last week and before that busy working on internal stuff.
I should be able to upload a new patch today.
bq. An actual mini-cluster test that mimics an MR job submitter and task's call
pattern would also be good.
I was able to address all the review comments except the above one.
Only way I can think to mimic job submitter is by creating MiniYARNCluster. I
don't have any experience writing yarn tests. I may take additional time if you
want me to write miniyarn cluster test.
[~yzhangal], [~andrew.wang]: Any pointers would be appreciated.
> 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
>
>
> 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]
