[
https://issues.apache.org/jira/browse/YARN-4108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15034353#comment-15034353
]
Wangda Tan commented on YARN-4108:
----------------------------------
Thanks for sharing your thoughts, [~bikassaha]!
I've done a POC very similar to your proposal and uploaded.
The major difference between my approach and your approach is: I prefer to do
the resource request matching within scheduler's allocation logic, so we don't
have to add a separate "scan" logic to match pending resource request and
to-be-preempted containers. With this approach, preemption logic and allocation
logic will be synchronized: we will ensure every preempted container can be
used by apps from under-satisfied queues, and progressively reaching the "ideal
allocation" calculated by preemption policy.
Please kindly review.
> CapacityScheduler: Improve preemption to preempt only those containers that
> would satisfy the incoming request
> --------------------------------------------------------------------------------------------------------------
>
> Key: YARN-4108
> URL: https://issues.apache.org/jira/browse/YARN-4108
> Project: Hadoop YARN
> Issue Type: Bug
> Components: capacity scheduler
> Reporter: Wangda Tan
> Assignee: Wangda Tan
> Attachments: YARN-4108-design-doc-v1.pdf, YARN-4108.poc.1.patch
>
>
> This is sibling JIRA for YARN-2154. We should make sure container preemption
> is more effective.
> *Requirements:*:
> 1) Can handle case of user-limit preemption
> 2) Can handle case of resource placement requirements, such as: hard-locality
> (I only want to use rack-1) / node-constraints (YARN-3409) / black-list (I
> don't want to use rack1 and host\[1-3\])
> 3) Can handle preemption within a queue: cross user preemption (YARN-2113),
> cross applicaiton preemption (such as priority-based (YARN-1963) /
> fairness-based (YARN-3319)).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
