[
https://issues.apache.org/jira/browse/YARN-927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13709359#comment-13709359
]
Sandy Ryza commented on YARN-927:
---------------------------------
Removing the ability to request multiple containers would be an annoying
regression for a large class of applications that merely want a
non-locality-constrained bunch of processes on the cluster. Have you
considered allowing StoredContainerRequest to have multiple containers and
including a decrementContainerRequest method?
> Change ContainerRequest to not have more than 1 container count and remove
> StoreContainerRequest
> ------------------------------------------------------------------------------------------------
>
> Key: YARN-927
> URL: https://issues.apache.org/jira/browse/YARN-927
> Project: Hadoop YARN
> Issue Type: Task
> Reporter: Bikas Saha
> Assignee: Bikas Saha
>
> The downside is having to use more than 1 container request when requesting
> more than 1 container at * priority. For most other use cases that have
> specific locations we anyways need to make multiple container requests. This
> will also remove unnecessary duplication caused by StoredContainerRequest. It
> will make the getMatchingRequest() always available and easy to use
> removeContainerRequest().
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
