You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Arun Suresh (JIRA)" <ji...@apache.org> on 2016/08/24 21:24:20 UTC
[jira] [Commented] (YARN-5532) Make ResourceLocalizationService
inside NodeManager independent of containers
[ https://issues.apache.org/jira/browse/YARN-5532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15435735#comment-15435735 ]
Arun Suresh commented on YARN-5532:
-----------------------------------
This is definitely useful.
Some initial comments:
# If you do make Resource Localization independent of containers, against who would the resources (mem, iobandwidth, storage etc) be accounted against ?
# Will this be a service exposed to any container running in the NM ? Which implies, we would have to incorporate a new NM <-> container protocol. Or will it be part of the ContainerManagementProtocol, in which case there are 2 options:
## allow only the AM to talk to the NM, and Containers route resource localization requests to the AM which asks the NM to download and then notify the requesting Container when complete
## NM shares a token with every container it starts which is subsequently used by the Container to invoke new methods in the ContainerManagementProtocol.
> Make ResourceLocalizationService inside NodeManager independent of containers
> -----------------------------------------------------------------------------
>
> Key: YARN-5532
> URL: https://issues.apache.org/jira/browse/YARN-5532
> Project: Hadoop YARN
> Issue Type: New Feature
> Reporter: Jian He
> Assignee: Jian He
>
> The goal is to enable NodeManagers to localize resources while container is running. Today, resource-localization is always the first step before starting a container. It will be useful if YARN can localize the resources continuously even while container is running.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org