[
https://issues.apache.org/jira/browse/MAPREDUCE-4417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13411696#comment-13411696
]
eric baldeschwieler commented on MAPREDUCE-4417:
------------------------------------------------
Anyone I've talked to who has been concerned about over the wire has also raise
the on disk issue. So, would it be better to put the encryption where we write
to disk, where we already compress? It seems like this might be less invasive
and would be more complete.
It has downsides if you do lots of spills, but it is much more complete. The
compaction issue can be addressed by collation work folks are already playing
with down the road.
---
Do you already have an HDFS solution in place? This only covers a fraction of
the data traffic.
> add support for encrypted shuffle
> ---------------------------------
>
> Key: MAPREDUCE-4417
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4417
> Project: Hadoop Map/Reduce
> Issue Type: New Feature
> Components: mrv2, security
> Affects Versions: 2.0.0-alpha
> Reporter: Alejandro Abdelnur
> Assignee: Alejandro Abdelnur
> Fix For: 2.0.1-alpha
>
>
> Currently Shuffle fetches go on the clear. While Kerberos provides
> comprehensive authentication for the cluster, it does not provide
> confidentiality.
> When processing sensitive data confidentiality may be desired (at the expense
> of job performance and resources utilization for doing encryption).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
