[
https://issues.apache.org/jira/browse/YARN-1492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14042847#comment-14042847
]
Chris Trezzo commented on YARN-1492:
------------------------------------
All patches for the API and cache manager are now up. I will now start breaking
out the client side changes and the Node Manager upload service changes. The
patch commit order is in order of the subtasks (I have also linked to dependent
issues in each of the subtasks).
I also wanted to mention that all the code for the shared cache project was a
collaboration between [~sjlee0], [~mingma] and myself.
> truly shared cache for jars (jobjar/libjar)
> -------------------------------------------
>
> Key: YARN-1492
> URL: https://issues.apache.org/jira/browse/YARN-1492
> Project: Hadoop YARN
> Issue Type: New Feature
> Affects Versions: 2.0.4-alpha
> Reporter: Sangjin Lee
> Assignee: Chris Trezzo
> Attachments: YARN-1492-all-trunk-v1.patch, shared_cache_design.pdf,
> shared_cache_design_v2.pdf, shared_cache_design_v3.pdf,
> shared_cache_design_v4.pdf, shared_cache_design_v5.pdf
>
>
> Currently there is the distributed cache that enables you to cache jars and
> files so that attempts from the same job can reuse them. However, sharing is
> limited with the distributed cache because it is normally on a per-job basis.
> On a large cluster, sometimes copying of jobjars and libjars becomes so
> prevalent that it consumes a large portion of the network bandwidth, not to
> speak of defeating the purpose of "bringing compute to where data is". This
> is wasteful because in most cases code doesn't change much across many jobs.
> I'd like to propose and discuss feasibility of introducing a truly shared
> cache so that multiple jobs from multiple users can share and cache jars.
> This JIRA is to open the discussion.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
