Wangda Tan commented on YARN-3885:

You can see the log:
NAME: queueA CUR: <memory:209, vCores:0> PEN: <memory:0, vCores:0> GAR: 
<memory:200, vCores:0> NORM: 1.0 IDEAL_ASSIGNED: <memory:201, vCores:1> 
IDEAL_PREEMPT: <memory:8, vCores:-1> ACTUAL_PREEMPT: <memory:0, vCores:0> 
UNTOUCHABLE: <memory:0, vCores:0> PREEMPTABLE: <memory:10, vCores:0>
queuA's extra is 9, but preemptable is 10, this could lead mis computing 
preemptable for A's parent queues. (preemptableExtra is used to compute 
untouchableExtra, and untouchableExtra is used to compute ideal_allocation). In 
your case is fine, but imagining there're some hierarchy above queueA, policy 
can preempt containers from a queue more than needed.

> ProportionalCapacityPreemptionPolicy doesn't preempt if queue is more than 2 
> level
> ----------------------------------------------------------------------------------
>                 Key: YARN-3885
>                 URL: https://issues.apache.org/jira/browse/YARN-3885
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: yarn
>    Affects Versions: 2.8.0
>            Reporter: Ajith S
>            Assignee: Ajith S
>            Priority: Blocker
>         Attachments: YARN-3885.02.patch, YARN-3885.03.patch, 
> YARN-3885.04.patch, YARN-3885.patch
> when preemption policy is {{ProportionalCapacityPreemptionPolicy.cloneQueues}}
> this piece of code, to calculate {{untoucable}} doesnt consider al the 
> children, it considers only immediate childern

This message was sent by Atlassian JIRA

Reply via email to