[
https://issues.apache.org/jira/browse/YARN-2498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wangda Tan updated YARN-2498:
-----------------------------
Description:
There're 3 stages in ProportionalCapacityPreemptionPolicy,
# Recursively calculate {{ideal_assigned}} for queue. This is depends on
available resource, resource used/pending in each queue and guaranteed capacity
of each queue.
# Mark to-be preempted containers: For each over-satisfied queue, it will mark
some containers will be preempted.
# Notify scheduler about to-be preempted container.
We need respect labels in the cluster for both #1 and #2:
For #1, when calculating ideal_assigned for each queue, we need get
by-partition-ideal-assigned according to queue's
guaranteed/maximum/used/pending resource on specific partition.
For #2, when we make decision about whether we need preempt a container, we
need make sure, resource this container is *possibly* usable by a queue which
is under-satisfied and has pending resource.
In addition, we need to handle ignore_partition_exclusivity case, when we need
to preempt containers from a queue's partition, we will first preempt
ignore_partition_exclusivity allocated containers.
was:
There're 3 stages in ProportionalCapacityPreemptionPolicy,
# Recursively calculate {{ideal_assigned}} for queue. This is depends on
available resource, resource used/pending in each queue and guaranteed capacity
of each queue.
# Mark to-be preempted containers: For each over-satisfied queue, it will mark
some containers will be preempted.
# Notify scheduler about to-be preempted container.
We need respect labels in the cluster for both #1 and #2:
For #1, when there're some resource available in the cluster, we shouldn't
assign it to a queue (by increasing {{ideal_assigned}}) if the queue cannot
access such labels
For #2, when we make decision about whether we need preempt a container, we
need make sure, resource this container is *possibly* usable by a queue which
is under-satisfied and has pending resource.
> Respect labels in preemption policy of capacity scheduler
> ---------------------------------------------------------
>
> Key: YARN-2498
> URL: https://issues.apache.org/jira/browse/YARN-2498
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: resourcemanager
> Reporter: Wangda Tan
> Assignee: Wangda Tan
> Attachments: STALED-YARN-2498.zip, YARN-2498.1.patch
>
>
> There're 3 stages in ProportionalCapacityPreemptionPolicy,
> # Recursively calculate {{ideal_assigned}} for queue. This is depends on
> available resource, resource used/pending in each queue and guaranteed
> capacity of each queue.
> # Mark to-be preempted containers: For each over-satisfied queue, it will
> mark some containers will be preempted.
> # Notify scheduler about to-be preempted container.
> We need respect labels in the cluster for both #1 and #2:
> For #1, when calculating ideal_assigned for each queue, we need get
> by-partition-ideal-assigned according to queue's
> guaranteed/maximum/used/pending resource on specific partition.
> For #2, when we make decision about whether we need preempt a container, we
> need make sure, resource this container is *possibly* usable by a queue which
> is under-satisfied and has pending resource.
> In addition, we need to handle ignore_partition_exclusivity case, when we
> need to preempt containers from a queue's partition, we will first preempt
> ignore_partition_exclusivity allocated containers.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
