[
https://issues.apache.org/jira/browse/YUNIKORN-2457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Craig Condit updated YUNIKORN-2457:
-----------------------------------
Description: The core scheduler currently tracks asks and allocations
separately. Historically, this was to allow a one-to-many relationship between
asks and allocations via the maxAllocations field. However, this logic has
never been utilized and causes a lot of special-casing and friction. If we
remove maxAllocations, we can unify the ask and allocation objects and simplify
the scheduler-interface and tracking facilities. (was: The core scheduler
currently tracks asks and allocations separately. Historically, this was to
allow a one-to-many relationship between asks and allocations via the askRepeat
field. However, this logic has never been utilized and causes a lot of
special-casing and friction. If we remove askRepeat, we can unify the ask and
allocation objects and simplify the scheduler-interface and tracking
facilities.)
> [UMBRELLA] Unify ask and allocation
> -----------------------------------
>
> Key: YUNIKORN-2457
> URL: https://issues.apache.org/jira/browse/YUNIKORN-2457
> Project: Apache YuniKorn
> Issue Type: Improvement
> Components: core - scheduler, scheduler-interface, shim - kubernetes
> Reporter: Craig Condit
> Assignee: Craig Condit
> Priority: Major
>
> The core scheduler currently tracks asks and allocations separately.
> Historically, this was to allow a one-to-many relationship between asks and
> allocations via the maxAllocations field. However, this logic has never been
> utilized and causes a lot of special-casing and friction. If we remove
> maxAllocations, we can unify the ask and allocation objects and simplify the
> scheduler-interface and tracking facilities.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
