hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wangda Tan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-1197) Support changing resources of an allocated container
Date Wed, 17 Jun 2015 00:06:06 GMT

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

Wangda Tan commented on YARN-1197:

The latest proposal (https://issues.apache.org/jira/browse/YARN-1197?focusedCommentId=14588963&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14588963)
makes sense to me. 

bq. We definitely need AllocateResponseProto for container increase token. For decrease result,
it is optional, but probably it doesn't hurt to set it anyway.
I suggest we only include token when it's necessary, we can add token to decrease result when
we needed.

bq. We could just use the existing getContainerStatus() API for doing this polling for now.
+1, we don't need a new API.

[~sandyr], do you agree with the latest proposal?

> Support changing resources of an allocated container
> ----------------------------------------------------
>                 Key: YARN-1197
>                 URL: https://issues.apache.org/jira/browse/YARN-1197
>             Project: Hadoop YARN
>          Issue Type: Task
>          Components: api, nodemanager, resourcemanager
>    Affects Versions: 2.1.0-beta
>            Reporter: Wangda Tan
>         Attachments: YARN-1197 old-design-docs-patches-for-reference.zip, YARN-1197_Design.pdf
> The current YARN resource management logic assumes resource allocated to a container
is fixed during the lifetime of it. When users want to change a resource 
> of an allocated container the only way is releasing it and allocating a new container
with expected size.
> Allowing run-time changing resources of an allocated container will give us better control
of resource usage in application side

This message was sent by Atlassian JIRA

View raw message