[
https://issues.apache.org/jira/browse/YUNIKORN-2507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikandan R updated YUNIKORN-2507:
-----------------------------------
Description:
Queue setup: root.family.parent.child[1-2]
Max res has been set on parent queue. Say, 10GB. Usage is slightly lesser. Say,
9GB. Ask1 (say, 2 GB) had come in for Child1 Queue whose usage is already
lesser than its guaranteed quota. So there is a need for preemption. In this
case, fence selection/queue selection should not go outside the parent queue
hierarchy and queues in the same level as parent (parent queue's siblings)
should not be considered at all as accommodating the ask somewhere in parent
siblings hierarchy would violate the max resource quota of parent queue.
was:
Queue setup: root.family.parent.child[1-2]
Max res has been set on parent queue. Say, 10GB. Usage is slightly lesser. Say,
9GB. Ask1 (say, 2 GB) had come in for Child1 Queue whose usage is already
greater than its guaranteed quota (borrowed by some other child queues). So
there is a need for preemption. In this case, fence selection/queue selection
should not go outside the parent queue hierarchy and queues in the same level
as parent (parent queue's siblings) should not be considered at all as
accommodating the ask somewhere in parent siblings hierarchy would violate the
max resource quota of parent queue.
> Picking Victims should consider usage and max quota for queues at each level
> ----------------------------------------------------------------------------
>
> Key: YUNIKORN-2507
> URL: https://issues.apache.org/jira/browse/YUNIKORN-2507
> Project: Apache YuniKorn
> Issue Type: Sub-task
> Components: core - scheduler
> Reporter: Manikandan R
> Assignee: Manikandan R
> Priority: Major
>
> Queue setup: root.family.parent.child[1-2]
> Max res has been set on parent queue. Say, 10GB. Usage is slightly lesser.
> Say, 9GB. Ask1 (say, 2 GB) had come in for Child1 Queue whose usage is
> already lesser than its guaranteed quota. So there is a need for preemption.
> In this case, fence selection/queue selection should not go outside the
> parent queue hierarchy and queues in the same level as parent (parent queue's
> siblings) should not be considered at all as accommodating the ask somewhere
> in parent siblings hierarchy would violate the max resource quota of parent
> queue.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]