[
https://issues.apache.org/jira/browse/YARN-4945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15392184#comment-15392184
]
Eric Payne commented on YARN-4945:
----------------------------------
Thanks [~sunilg]. I appreciate very much any design help and POC help that you
can provide.
{quote}
queue preemption may need to consider multiple factors such
- Priority
- Fairness
- User limit
{quote}
In general, I would like to separate out the sub-feature pieces of in-queue
preemption as much as possible. I am a fan of making small, simple improvements
in increments. I believe this makes it easier to understand, test, and review.
bq. For initial POC, I was planning priority as I have done an independent POC
for priority preemption alone.
One thing I don't understand is the use case for a priority policy that is
separate from a user limit policy. For my users' use case, the most important
of these is user limit. However, I think that in-queue preemption based on user
limit needs to be very dependent on app priority and vice-versa. Can you please
elaborate?
> [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
>
> 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]
