hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Craig Welch (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3632) Ordering policy should be allowed to reorder an application when demand changes
Date Fri, 15 May 2015 20:15:00 GMT

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

Craig Welch commented on YARN-3632:

Uploaded patch to address checkstyle and whitespace concerns and to move queue acquisition
from app inside the app syncronization.  javac error unrelated, for an untouched class.  
[WARNING] /home/jenkins/jenkins-slave/workspace/PreCommit-YARN-Build/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/TestRMRestart.java:[2171,32]
[unchecked] Possible heap pollution from parameterized vararg type E
[WARNING]   where E is a type-variable:
Findbugs also appears unrelated, no changes appear to call into the area where the concern
lies (it looks similar to the javac location, as though it missed a commit in the comparison??)

> Ordering policy should be allowed to reorder an application when demand changes
> -------------------------------------------------------------------------------
>                 Key: YARN-3632
>                 URL: https://issues.apache.org/jira/browse/YARN-3632
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: capacityscheduler
>            Reporter: Craig Welch
>            Assignee: Craig Welch
>         Attachments: YARN-3632.0.patch, YARN-3632.1.patch, YARN-3632.3.patch, YARN-3632.4.patch
> At present, ordering policies have the option to have an application re-ordered (for
allocation and preemption) when it is allocated to or a container is recovered from the application.
 Some ordering policies may also need to reorder when demand changes if that is part of the
ordering comparison, this needs to be made available (and used by the fairorderingpolicy when
sizebasedweight is true)

This message was sent by Atlassian JIRA

View raw message