[
https://issues.apache.org/jira/browse/YUNIKORN-2791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Bacsko resolved YUNIKORN-2791.
------------------------------------
Fix Version/s: 1.7.0
Resolution: Fixed
> [Umbrella] Tracking non-Yunikorn allocations in the core
> --------------------------------------------------------
>
> Key: YUNIKORN-2791
> URL: https://issues.apache.org/jira/browse/YUNIKORN-2791
> Project: Apache YuniKorn
> Issue Type: New Feature
> Components: core - scheduler, scheduler-interface, shim - kubernetes
> Reporter: Peter Bacsko
> Assignee: Peter Bacsko
> Priority: Major
> Labels: release-notes
> Fix For: 1.7.0
>
>
> Currently, we don't know what non-YK pods are assigned to a particular node
> in the core. We only track the total amount of allocations as
> {{occupiedResources}} object inside the {{objects.Node}} type. If the
> tracking somehow becomes out of sync with the actual cluster state, it's very
> difficult to know what went wrong, because these allocations are not shown in
> the state dump.
> In order to enhance supportability, we want to track all non-YK pods per node
> on the core side.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
