[
https://issues.apache.org/jira/browse/YARN-1197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13831835#comment-13831835
]
Bikas Saha commented on YARN-1197:
----------------------------------
This is great. However, for efficient review/commit we will need to break these
down into different jiras and attach patches to them. That will force us to
look at each change by itself (using this jira for context) and more
importantly, make sure each logically distinct piece is complete in itself. It
should have its own tests, and pass Jenkins build/test independently so that it
can be committed independently.
Can you please do that and determine the order in which those jiras should be
reviewed/committed. e.g. the API and protobuf changes should be a separate jira
for RM and NM protocols. That should probably be the first jira we should
review. And so on.
> 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
>
>
> Currently, YARN cannot support merge several containers in one node to a big
> container, which can make us incrementally ask resources, merge them to a
> bigger one, and launch our processes. The user scenario is described in the
> comments.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
