[
https://issues.apache.org/jira/browse/YARN-1016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13732717#comment-13732717
]
Kam Kasravi commented on YARN-1016:
-----------------------------------
Thanks Steve, Jason. I looked at ResourceLocalizationService.PublicLocalizer
and I'm still a bit unclear whether resources provided by the YARN client as
public
are necessarily shared across different YARN containers since they would need
to use common paths. For example if client1 uploads a resource named
foo/baz.jar and client2
uploads a resource named bar/baz.jar and both indicate that baz.jar is a public
resource would it be shared across different containers?
If no, then is there value in attempting to do so? I imagine the answer is no
since there is no guarantee these resources are in fact the same. However,
given a slightly
different example where client1 uses a resource which comes from
~/.m2/repository/foo/baz/0.3/baz-0.3.jar and client2 uses the same resource
(both use maven and
these resources came from the public maven repo) - is there value in attempting
to map this common resource to hdfs://repository/foo/baz/0.3/baz-0.3.jar?
> Define a HDFS based repository that allows YARN services to share resources
> ---------------------------------------------------------------------------
>
> Key: YARN-1016
> URL: https://issues.apache.org/jira/browse/YARN-1016
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: api
> Affects Versions: 3.0.0
> Reporter: Kam Kasravi
>
> YARN services both short and long lived can benefit from a resource repo
> rather than packaging resources within the YARN client to be extracted and
> used by the Application Master and (later) the containers. Standardizing a
> resource repo will provide performance benefits as well. The repo should be
> similar to maven or ivy repo's so discovery and versioning are built-in.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
