[ https://issues.apache.org/jira/browse/YARN-1197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13837559#comment-13837559 ]
Wangda Tan commented on YARN-1197: ---------------------------------- +1 for Junping's idea, I'm not sure if we can get low-latency container increase via resource over-commitment which needed by many applications. > 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 > Assignee: Wangda Tan > Attachments: mapreduce-project.patch.ver.1, > tools-project.patch.ver.1, yarn-1197-v2.pdf, yarn-1197-v3.pdf, > yarn-1197-v4.pdf, yarn-1197.pdf, yarn-api-protocol.patch.ver.1, > yarn-pb-impl.patch.ver.1, yarn-server-common.patch.ver.1, > yarn-server-nodemanager.patch.ver.1, yarn-server-resourcemanager.patch.ver.1 > > > 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 (v6.1#6144)