hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-1503) Support making additional 'LocalResources' available to running containers
Date Wed, 24 Aug 2016 17:25:20 GMT

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

Vinod Kumar Vavilapalli commented on YARN-1503:

[~jianhe], [~asuresh], [~vvasudev],

This got a little too confusing.

I just (a) edited the title of this JIRA to what it was originally, and (b) reopened YARN-5532,
editing its title to what it originally targeted.

How about we do the following?
 - Use YARN-5532 to build the basic building block of ResourceLocalization as an independent
unit inside the NM. Today, it is wired into Container's state-machine. The goal is to make
it first-class so that multiple parties like upgrades, continuous localization can use this
core localization service.
 - Use YARN-1503 - this JIRA - to define and implement APIs for continuous localization.
 - Use YARN-4876 to define and implement APIs needed for upgrades, and also the corresponding
Container state machine changes.


> Support making additional 'LocalResources' available to running containers
> --------------------------------------------------------------------------
>                 Key: YARN-1503
>                 URL: https://issues.apache.org/jira/browse/YARN-1503
>             Project: Hadoop YARN
>          Issue Type: Improvement
>            Reporter: Siddharth Seth
>            Assignee: Jian He
>         Attachments: Continuous-resource-localization.pdf
> We have a use case, where additional resources (jars, libraries etc) need to be made
available to an already running container. Ideally, we'd like this to be done via YARN (instead
of having potentially multiple containers per node download resources on their own).
> Proposal:
>   NM to support an additional API where a list of resources can be specified. Something
like "localiceResource(ContainerId, Map<String, LocalResource>)
>   NM would also require an additional API to get state for these resources - "getLocalizationState(ContainerId)"
- which returns the current state of all local resources for the specified container(s).

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org

View raw message