hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-6144) FairScheduler: preempted resources can become negative
Date Fri, 10 Feb 2017 00:09:42 GMT

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

Hudson commented on YARN-6144:

SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #11229 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/11229/])
YARN-6144. FairScheduler: preempted resources can become negative. (kasha: rev 08f93978f3ec724b24a93d7ef538f158da75802f)
* (edit) hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fair/FSAppAttempt.java
* (edit) hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fair/TestFairScheduler.java

> FairScheduler: preempted resources can become negative
> ------------------------------------------------------
>                 Key: YARN-6144
>                 URL: https://issues.apache.org/jira/browse/YARN-6144
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: fairscheduler, resourcemanager
>    Affects Versions: 3.0.0-alpha2
>            Reporter: Miklos Szegedi
>            Assignee: Miklos Szegedi
>            Priority: Blocker
>             Fix For: 2.9.0, 3.0.0-alpha3
>         Attachments: Screen Shot 2017-02-02 at 12.49.14 PM.png, YARN-6144.000.patch,
YARN-6144.001.patch, YARN-6144.002.patch, YARN-6144.003.patch
> {{preemptContainers()}} calls {{trackContainerForPreemption()}} to collect the list of
containers and resources that were preempted for an application. Later the list is reduced
when {{containerCompleted()}} calls {{untrackContainerForPreemption()}}. The bug is that the
resource variable {{preemptedResources}} is subtracted, not just when the container was preempted
but also when it has completed successfully. This causes that we return an incorrect value
in {{getResourceUsage()}}.

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