[
https://issues.apache.org/jira/browse/YARN-11108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17517935#comment-17517935
]
Juanjuan Tian edited comment on YARN-11108 at 3/23/23 5:46 AM:
----------------------------------------------------------------
When calculating accepted, current formula is
Resource.min (Resources.min(rc, clusterResource, avail,
Resources.subtract(Resources.add(getUsed(),(considersReservedResource ? pending
: pendingDeductReserved)), idealAssigned))) is used, but this can lead that
accepted resource is bigger than its pending resource, for example, when
cluster resource is (32GB, 16cores), available is (2GB, 3cores), Resources.
.subtract(Resources.add(getUsed(),
(considersReservedResource ? pending : pendingDeductReserved)),
idealAssigned))) is (8GB, 2cores)
after the calculation, the accepted is (2GB, 3cores), accepted cpu is bigger
than its pending cpu number
Resources.componentwiseMin (Resources.componentwiseMin(avail,
Resources.subtract(Resources.add(getUsed(), (considersReservedResource ?
pending : pendingDeductReserved)), idealAssigned))))) should be used,
!image-2022-04-06-16-29-57-871.png!
was (Author: jutia):
When calculating accepted,
Resource.min (Resources.min(rc, clusterResource, avail,
Resources.subtract(Resources.add(getUsed(),(considersReservedResource ? pending
: pendingDeductReserved)), idealAssigned))) is used,
but Resources.componentwiseMin (Resources.componentwiseMin(avail,
Resources.subtract(Resources.add(getUsed(), (considersReservedResource ?
pending : pendingDeductReserved)), idealAssigned))))) should be used,
for example, if cluster resource is (32GB, 16cores), available is (2GB,
3cores), Resources.
.subtract(Resources.add(getUsed(),
(considersReservedResource ? pending : pendingDeductReserved)),
idealAssigned))) is (8GB, 2cores)
after the calculation, the accepted is (2GB, 3cores), accepted cpu is bigger
than its pending cpu number
!image-2022-04-06-16-29-57-871.png!
> Unexpected preemptions happen when hierarchy queues case
> --------------------------------------------------------
>
> Key: YARN-11108
> URL: https://issues.apache.org/jira/browse/YARN-11108
> Project: Hadoop YARN
> Issue Type: Improvement
> Affects Versions: 2.9.2
> Reporter: Juanjuan Tian
> Assignee: Juanjuan Tian
> Priority: Major
> Attachments: image-2022-04-06-16-29-57-871.png
>
>
> Found unexpected preemptions happen when hierarchy queues case, the issue is
> that a sub queue can accept resource more than used+pending, leading to other
> queues {color:#172b4d}IDEAL_ASSIGNED is smaller than used + pending, and
> preemptions happen unexpectedly {color}
>
> 2022-04-02T01:11:12,973 DEBUG [SchedulingMonitor
> (ProportionalCapacityPreemptionPolicy)]
> org.apache.hadoop.yarn.server.resourcemanager.monitor.capacity.PreemptableResourceCalculator:
> NAME: MSANRPAB PARTITION: persistent{color:#de350b} CUR: <memory:37934080,
> vCores:8285, ports:null{color}, [<groupIndex:1, availableCpuCount:-36467,
> reservedAffinity:\\{6, 8, 9, 10, 11, 15, 19, 20, 22, 24, 28}>]> PEN:
> <memory:0, vCores:0, ports:null> TOTAL_PEN: <memory:0, vCores:0, ports:null>
> RESERVED: <memory:0, vCores:0, ports:null> GAR: <memory:30720000,
> vCores:9571, ports:null> NORM: 0.3424696922302246{color:#de350b}
> IDEAL_ASSIGNED: <memory:37934080, vCores:8903, ports:null>{color}
> IDEAL_PREEMPT: <memory:0, vCores:0, ports:null> ACTUAL_PREEMPT: <memory:0,
> vCores:0, ports:null> UNTOUCHABLE: <memory:0, vCores:0, ports:null>
> PREEMPTABLE: <memory:7214080, vCores:-1286, ports:null, [<groupIndex:1,
> availableCpuCount:-36467, reservedAffinity:\\{6, 8, 9, 10, 11, 15, 19, 20,
> 22, 24, 28}>]> BONUS_WEIGHT: -1.0
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
