hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Payne (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-2113) Add cross-user preemption within CapacityScheduler's leaf-queue
Date Tue, 11 Jul 2017 21:09:00 GMT

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

Eric Payne commented on YARN-2113:

I should not have created a separate patch for the branch-2 backport. The branch-2.8 backport
is fine, but not the branch-2 one.

[~sunilg], [~leftnoteasy], [~jlowe]:

If no one objects, I will do the following:
# Revert the commit for branch-2 YARN-2113.branch-2.0020.patch (eda4ac0)
# Cherry pick YARN-5889 to branch-2 from trunk
# Cherry pick YARN-2113 to branch-2 from trunk

I have done this in my local repo and it comes back fairly cleanly.

Here is what happened:
In trunk, the intra-queue preemption feature depends on the following:
- YARN-3140: Improve locks in AbstractCSQueue/LeafQueue/ParentQueue
- YARN-5889: Improve and refactor user-limit calculation in capacity scheduler

I thought that YARN-3140 had not been backported to either branch-2 nor branch-2.8. I attempted
to cherry-pick YARN-3140 to branch-2.8 but had several deadlock issues. Therefore, I made
the decision to create a separate branch-2.8 patch.

 I thought I needed to do the same thing for branch-2, but I did not. YARN-3140 has been cherry-picked
to branch-2.

> Add cross-user preemption within CapacityScheduler's leaf-queue
> ---------------------------------------------------------------
>                 Key: YARN-2113
>                 URL: https://issues.apache.org/jira/browse/YARN-2113
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: capacity scheduler
>            Reporter: Vinod Kumar Vavilapalli
>            Assignee: Sunil G
>             Fix For: 2.9.0, 3.0.0-alpha4, 2.8.3
>         Attachments: IntraQueue Preemption-Impact Analysis.pdf, TestNoIntraQueuePreemptionIfBelowUserLimitAndDifferentPrioritiesWithExtraUsers.txt,
YARN-2113.0001.patch, YARN-2113.0002.patch, YARN-2113.0003.patch, YARN-2113.0004.patch, YARN-2113.0005.patch,
YARN-2113.0006.patch, YARN-2113.0007.patch, YARN-2113.0008.patch, YARN-2113.0009.patch, YARN-2113.0010.patch,
YARN-2113.0011.patch, YARN-2113.0012.patch, YARN-2113.0013.patch, YARN-2113.0014.patch, YARN-2113.0015.patch,
YARN-2113.0016.patch, YARN-2113.0017.patch, YARN-2113.0018.patch, YARN-2113.0019.patch, YARN-2113.apply.onto.0012.ericp.patch,
YARN-2113.branch-2.0019.patch, YARN-2113.branch-2.0020.patch, YARN-2113.branch-2.8.0019.patch,
YARN-2113.branch-2.8.0020.patch, YARN-2113 Intra-QueuePreemption Behavior.pdf, YARN-2113.v0.patch
> Preemption today only works across queues and moves around resources across queues per
demand and usage. We should also have user-level preemption within a queue, to balance capacity
across users in a predictable manner.

This message was sent by Atlassian JIRA

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

View raw message