hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-1016) Define a HDFS based repository that allows YARN services to share resources
Date Wed, 07 Aug 2013 20:15:48 GMT

    [ https://issues.apache.org/jira/browse/YARN-1016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13732682#comment-13732682

Steve Loughran commented on YARN-1016:

I didn't know that. If that's the case, that should be all that is needed. Resource sharing
becomes a simple matter of a project/app setting up a directory in HDFS.

Karn -were you thinking of having all the Maven JARs there, so that instead of grabbing JAR
files locally, you just say ("org.apache.log4j","log4j","1.12.16") and have it pulled in?
For apps that are deployed JAR-by-JAR that could be useful. Again, you could just do this
with a shared directory tree -if you don't want dependency metadata it's pretty trivial to
set this up.

Now, if you want this repository to be shared across applications -including 3rd party ones-
that's where you could have some formal structure. Even so, I could imagine doing this via
a helper library that the client or AM could invoke (ignoring specifics of how to find files).
The actual Ivy libraries would be the place to start here, as it is designed to work outside
> 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

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

View raw message