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-2498) [YARN-796] Respect labels in preemption policy of capacity scheduler
Date Wed, 17 Sep 2014 09:11:34 GMT

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

Hadoop QA commented on YARN-2498:
---------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12669372/yarn-2498-implementation-notes.pdf
  against trunk revision c0c7e6f.

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-YARN-Build/4989//console

This message is automatically generated.

> [YARN-796] Respect labels in preemption policy of capacity scheduler
> --------------------------------------------------------------------
>
>                 Key: YARN-2498
>                 URL: https://issues.apache.org/jira/browse/YARN-2498
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: resourcemanager
>            Reporter: Wangda Tan
>            Assignee: Wangda Tan
>         Attachments: YARN-2498.patch, YARN-2498.patch, yarn-2498-implementation-notes.pdf
>
>
> There're 3 stages in ProportionalCapacityPreemptionPolicy,
> # Recursively calculate {{ideal_assigned}} for queue. This is depends on available resource,
resource used/pending in each queue and guaranteed capacity of each queue.
> # Mark to-be preempted containers: For each over-satisfied queue, it will mark some containers
will be preempted.
> # Notify scheduler about to-be preempted container.
> We need respect labels in the cluster for both #1 and #2:
> For #1, when there're some resource available in the cluster, we shouldn't assign it
to a queue (by increasing {{ideal_assigned}}) if the queue cannot access such labels
> For #2, when we make decision about whether we need preempt a container, we need make
sure, resource this container is *possibly* usable by a queue which is under-satisfied and
has pending resource.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message