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

Jian He commented on YARN-1503:
-------------------------------

It is differentiated. To clarify, here, I'm referring to the re-localization 
process, not the normal localization. For normal container localization, we can 
keep the behavior the same as today. For re-localization, i.e. localize the 
resources while the container is running, the container should not fail if the 
localization process fails. The AM just gets notification that the localization 
failed, AM itself choose to ignore/retry or fail the task depending on the 
use-case.

> 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
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to