[
https://issues.apache.org/jira/browse/YARN-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15155829#comment-15155829
]
Inigo Goiri commented on YARN-1011:
-----------------------------------
[~kasha}, I think those can apply easily to {{CapacityScheduler}}. To get
started, I would take a first try in YARN-4511 with:
# Get the oversubscription ratio into {{SchedulerNode}}
# Add methods {{getUsedUtilizationResource()}} and
{{getAvailableUtilizationResource()}} for {{containersUtilization}} (which is
already available from YARN-3980 and would also use the oversubscription)
# Rename {{getUsedResource()}} to {{getUsedAllocationResource()}},
{{getAvailableResource()}} to {{getAvailableAllocationResource()}}, and
{{getTotalResource()}} to {{getTotalAllocationResource()}} (I don't think these
are external APIs so it should be fine to change the names)
For your 2, 3, and 4, we can add them to {{FairScheduler}} in YARN-1015 as a
first prototype and then move as much as possible to YARN-4511.
> [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, yarn-1011-design-v1.pdf,
> yarn-1011-design-v2.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)