[ 
https://issues.apache.org/jira/browse/YARN-2009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sunil G updated YARN-2009:
--------------------------
    Attachment: YARN-2009.0002.patch

Thanks [~eepayne] and [~leftnoteasy]. Attaching new patch.

Regarding user-limit discussion, i think generally approach looks fine. I feel 
we can also add dead-zone around user-limit. This can help to avoid thrashing 
scenarios. (we do need for priority as its kind of direct calculation).

I am also thinking case when we ll have a complete preemption use case like few 
containers coming from inter queue, and few others from user-limit, and finally 
some more containers coming from priority based policy.

I think we might  need to improve preemption metrics here. I would like to 
collect and design preemption metrics module so that we can get clear 
information about which module perform how much preemption. Thoughts?

> Priority support for preemption in ProportionalCapacityPreemptionPolicy
> -----------------------------------------------------------------------
>
>                 Key: YARN-2009
>                 URL: https://issues.apache.org/jira/browse/YARN-2009
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: capacityscheduler
>            Reporter: Devaraj K
>            Assignee: Sunil G
>         Attachments: YARN-2009.0001.patch, YARN-2009.0002.patch
>
>
> While preempting containers based on the queue ideal assignment, we may need 
> to consider preempting the low priority application containers first.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org

Reply via email to