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 Sun, 26 Jan 2014 08:42:47 GMT

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

Wangda Tan commented on YARN-1197:

I created a bunch of sub tasks for easier review, 
NM side changes are: YARN-1643, YARN-1644, YARN-1645, instead of big task -- YARN-1449; I'll
work on them first.
RM side changes are: YARN-1646, YARN-1647, YARN-1648, YARN-1649, YARN-1650, YARN-1651, YARN-1652,
YARN-1653, YARN-1654, instead of big task -- YARN-1502. These sub tasks will add change container
resource support to capacity scheduler and change corresponding implementations in RM side;
I'll break-down existing patch in YARN-1502 and submit after changes in NM completed.
YARN-1655 will try to add support to fair scheduler, I plan to work on this after changes
in capacity scheduler completed.

> 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-scheduler-v1.pdf,
yarn-1197-v2.pdf, yarn-1197-v3.pdf, yarn-1197-v4.pdf, yarn-1197-v5.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,
> 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