hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Lowe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-4610) Reservations continue looking for one app causes other apps to starve
Date Wed, 20 Jan 2016 17:04:39 GMT

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

Jason Lowe commented on YARN-4610:

Forgot to mention that TestApplicationPriority is failing in the same way for other precommit
builds (e.g.: https://builds.apache.org/job/PreCommit-YARN-Build/10177/artifact/patchprocess/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-resourcemanager-jdk1.8.0_66.txt),
and only failed on one JDK version vs. another.  Couldn't find a tracking ticket for that
one, so I filed YARN-4614.

> Reservations continue looking for one app causes other apps to starve
> ---------------------------------------------------------------------
>                 Key: YARN-4610
>                 URL: https://issues.apache.org/jira/browse/YARN-4610
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: capacityscheduler
>    Affects Versions: 2.7.1
>            Reporter: Jason Lowe
>            Assignee: Jason Lowe
>            Priority: Blocker
>         Attachments: YARN-4610.001.patch
> CapacityScheduler's LeafQueue has "reservations continue looking" logic that allows an
application to unreserve elsewhere to fulfil a container request on a node that has available
space.  However in 2.7 that logic seems to break allocations for subsequent apps in the queue.
 Once a user hits its user limit, subsequent apps in the queue for other users receive containers
at a significantly reduced rate.

This message was sent by Atlassian JIRA

View raw message