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-3275) CapacityScheduler: Preemption happening on non-preemptable queues
Date Wed, 04 Mar 2015 22:20:40 GMT

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

Eric Payne updated YARN-3275:
    Attachment: YARN-3275.v2.txt

[~jlowe] and [~leftnoteasy], thank you for the reviews.

Attached is an updated patch (v2) with your suggested changes.

> CapacityScheduler: Preemption happening on non-preemptable queues
> -----------------------------------------------------------------
>                 Key: YARN-3275
>                 URL: https://issues.apache.org/jira/browse/YARN-3275
>             Project: Hadoop YARN
>          Issue Type: Bug
>    Affects Versions: 2.7.0
>            Reporter: Eric Payne
>            Assignee: Eric Payne
>              Labels: capacity-scheduler
>         Attachments: YARN-3275.v1.txt, YARN-3275.v2.txt
> YARN-2056 introduced the ability to turn preemption on and off at the queue level. In
cases where a queue goes over its absolute max capacity (YARN-3243, for example), containers
can be preempted from that queue, even though the queue is marked as non-preemptable.
> We are using this feature in large, busy clusters and seeing this behavior.

This message was sent by Atlassian JIRA

View raw message