hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (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 21:43:39 GMT

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

Hadoop QA commented on YARN-4610:
---------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} docker {color} | {color:blue} 0m 7s {color} | {color:blue}
Dockerfile '/home/jenkins/jenkins-slave/workspace/PreCommit-YARN-Build/dev-support/docker/Dockerfile'
not found, falling back to built-in. {color} |
| {color:red}-1{color} | {color:red} docker {color} | {color:red} 13m 55s {color} | {color:red}
Docker failed to build yetus/hadoop:date2016-01-20. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/12783421/YARN-4610.branch-2.7.001.patch
|
| JIRA Issue | YARN-4610 |
| Powered by | Apache Yetus 0.2.0-SNAPSHOT   http://yetus.apache.org |
| Console output | https://builds.apache.org/job/PreCommit-YARN-Build/10345/console |


This message was automatically generated.



> 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, YARN-4610.branch-2.7.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
(v6.3.4#6332)

Mime
View raw message