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

Sunil G commented on YARN-4945:
-------------------------------

Thanks [~eepayne] for the comments about the interaction b/w inter-queue and 
intra-queue together. Its a really a case to consider.

While working on POC, [~leftnoteasy] has mentioned about a case of 
normalization. We have to consider that inter-queue preemption is done while 
doing preemption calculation and selection for intra-queue. In the initial 
version of POC, i tried to achieve the basic framework and a working prototype. 
But for the version, we need to normalize pre-selected containers before each 
round in intra-queue preemption. (i think we can consider user-limit and 
priority only for now)
On the same note, we also need to consider case where selected containers are 
not rejected in subsequent rounds. Also if same containers are again 
re-selected in next rounds, we can consider those containers are already 
selected and deduct from resourceToObtain. These cases are handled as of today. 

I think I can add the impl details of this scenario also in the document so 
that it can come in first cut. Thoughts?

> [Umbrella] Capacity Scheduler Preemption Within a queue
> -------------------------------------------------------
>
>                 Key: YARN-4945
>                 URL: https://issues.apache.org/jira/browse/YARN-4945
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Wangda Tan
>         Attachments: Intra-Queue Preemption Use Cases.pdf, 
> IntraQueuepreemption-CapacityScheduler (Design).pdf, YARN-2009-wip.patch
>
>
> This is umbrella ticket to track efforts of preemption within a queue to 
> support features like:
> YARN-2009. YARN-2113. YARN-4781.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to