[
https://issues.apache.org/jira/browse/MAPREDUCE-7141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16739792#comment-16739792
]
Kuhu Shukla commented on MAPREDUCE-7141:
----------------------------------------
This patch is not perfect and has one big challenge. How do we decouple
ourselves for KMSSpillKeyProvider to not use the DistributedFileSystem for
getting the key provider shown below. What does it take for the RM to provide
an independent key provider.
{code}KeyProvider keyProvider =
((DistributedFileSystem)FileSystem.get(getConf())).getKeyProvider();
{code}
I appreciate any and all comments on the same.
> Allow KMS generated spill encryption keys
> -----------------------------------------
>
> Key: MAPREDUCE-7141
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-7141
> Project: Hadoop Map/Reduce
> Issue Type: Task
> Reporter: Kuhu Shukla
> Assignee: Kuhu Shukla
> Priority: Major
> Attachments: MAPREDUCE-7141-001.patch
>
>
> Currently the only way an encryption key for task spills is generated is by
> the AM's key generator. This JIRA tracks the work required to add KMS support
> to this key's generation allowing fault tolerance to AM failures/re-runs and
> also give another option to the client on how it wants the keys to be created.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
