[
https://issues.apache.org/jira/browse/YARN-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15072240#comment-15072240
]
Karthik Kambatla commented on YARN-1011:
----------------------------------------
bq. For resource oversubscription enable/disable for individual nodes, I think
it's very important since some nodes could be more important than others. Do
you think is it fine to add a configuration item to each NM's yarn-site.xml?
That is exactly the intent. Let us continue this conversation on YARN-4512.
bq. For scheduler-side implementation, instead of modifying individual
scheduler, I think we should try to add over-subscription policy to common
scheduling layer since it doesn't sounds very related to specific scheduler
implementation.
Makes sense. Doubt there is any scheduler-specific smarts here. If at all we
need to do them separately, it is most likely because our scheduler
abstractions are not clean.
> [Umbrella] Schedule containers based on utilization of currently allocated
> containers
> -------------------------------------------------------------------------------------
>
> Key: YARN-1011
> URL: https://issues.apache.org/jira/browse/YARN-1011
> Project: Hadoop YARN
> Issue Type: New Feature
> Reporter: Arun C Murthy
> Attachments: yarn-1011-design-v0.pdf
>
>
> Currently RM allocates containers and assumes resources allocated are
> utilized.
> RM can, and should, get to a point where it measures utilization of allocated
> containers and, if appropriate, allocate more (speculative?) containers.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
