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] [Updated] (YARN-4390) Do surgical preemption based on reserved container in CapacityScheduler
Date Tue, 06 Dec 2016 20:46:59 GMT

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

Eric Payne updated YARN-4390:
-----------------------------
    Attachment: YARN-4390.branch-2.8.002.patch

Thanks [~leftnoteasy].
{quote}
Thanks Eric Payne, if the TestCapacitySchedulerSurgicalPreemption passes locally for you,
please open a JIRA to track the UT failure and unblock the backport.
{quote}
YARN-5973
{quote}
And javac warnings / javadocs warnings looks related to the change, could you update the patch
accordingly?
{quote}
Attaching patch {{YARN-4390.branch-2.8.002.patch}}

I have backported these to branch 2.8 in my local repo. If you like, I can push them once
you approve of the patch.

> Do surgical preemption based on reserved container in CapacityScheduler
> -----------------------------------------------------------------------
>
>                 Key: YARN-4390
>                 URL: https://issues.apache.org/jira/browse/YARN-4390
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: capacity scheduler
>    Affects Versions: 2.8.0, 2.7.3, 3.0.0-alpha1
>            Reporter: Eric Payne
>            Assignee: Wangda Tan
>             Fix For: 2.9.0, 3.0.0-alpha1
>
>         Attachments: QueueNotHittingMax.jpg, YARN-4390-design.1.pdf, YARN-4390-test-results.pdf,
YARN-4390.1.patch, YARN-4390.2.patch, YARN-4390.3.branch-2.patch, YARN-4390.3.patch, YARN-4390.4.patch,
YARN-4390.5.patch, YARN-4390.6.patch, YARN-4390.7.patch, YARN-4390.8.patch, YARN-4390.branch-2.8.001.patch,
YARN-4390.branch-2.8.002.patch
>
>
> There are multiple reasons why preemption could unnecessarily preempt containers. One
is that an app could be requesting a large container (say 8-GB), and the preemption monitor
could conceivably preempt multiple containers (say 8, 1-GB containers) in order to fill the
large container request. These smaller containers would then be rejected by the requesting
AM and potentially given right back to the preempted app.



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

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


Mime
View raw message