[
https://issues.apache.org/jira/browse/YARN-1503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15437626#comment-15437626
]
Arun Suresh commented on YARN-1503:
-----------------------------------
bq. The re-localization process should not tie to container state-machine,
regardless whether the localization fails or succeed. Container continues to
run.
Hmmm... then shouldn't we differentiate between Relocalization and Localization
that is required to start the container ? Or are you proposing that the AM
calls the new localize API first and then startContainer only after it receives
a successful response. That way, we can maybe remove the Localization related
states in the NM Container state machine completely.. but that also means
existing AMs would need to be modified (or maybe we can just handle it in the
NMClient)
> 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]
