[ 
https://issues.apache.org/jira/browse/YARN-4108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14730222#comment-14730222
 ] 

Sunil G commented on YARN-4108:
-------------------------------

Hi [~leftnoteasy]
Overall I feel this logic sounds good.  I have some doubts though.
In Allocation logic, we will get {{Resource preemptable}} which is calculated 
by PCPP. Now as per this idea, Scheduler has to mark the containers for 
preemption from allocation thread. I feel, CS can approve that this much 
resource needs preemption. And PCPP in next round, can identify the containers 
for preemptions and can trigger the event. Or is there any other advantage of 
making to-be-preempted containers from allocation logic such as user-limit? 

> 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
>
> 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)

Reply via email to