[
https://issues.apache.org/jira/browse/YARN-1488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13854909#comment-13854909
]
Henry Robinson commented on YARN-1488:
--------------------------------------
Thanks for the clarifications. One further concern: when during the lifecycle
of a container do you imagine the delegation request might be made? It seems to
me that it would be best for the initial resource acquisition request to
indicate that the resource was to be delegated, and to which container, so that
there's no need to actually establish the source container only for it to be
immediately coalesced.
That is, I don't see right now a use case for delegating part-way through a
container's lifetime. As written (to the extent that I understand the protocols
at play) it looks to me like the proposed lifecycle is:
Resource request->Resource granted and container established (running some
process?)->Delegate request to NM->NM reworks the cgroups to implement the
request->Source container process is terminated
It might be better just to have:
Resource request (with delegation bits set)->Resource granted and NM
notified->NM assigns more resources to target container
Is that reasonable?
> Allow containers to delegate resources to another container
> -----------------------------------------------------------
>
> Key: YARN-1488
> URL: https://issues.apache.org/jira/browse/YARN-1488
> Project: Hadoop YARN
> Issue Type: New Feature
> Reporter: Arun C Murthy
>
> We should allow containers to delegate resources to another container. This
> would allow external frameworks to share not just YARN's resource-management
> capabilities but also it's workload-management capabilities.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
