You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@yunikorn.apache.org by "Kinga Marton (Jira)" <ji...@apache.org> on 2021/02/26 14:46:00 UTC
[jira] [Resolved] (YUNIKORN-547) Move TerminationType out of the
AllocationRelease message
[ https://issues.apache.org/jira/browse/YUNIKORN-547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kinga Marton resolved YUNIKORN-547.
-----------------------------------
Fix Version/s: 0.10
Resolution: Fixed
> Move TerminationType out of the AllocationRelease message
> ---------------------------------------------------------
>
> Key: YUNIKORN-547
> URL: https://issues.apache.org/jira/browse/YUNIKORN-547
> Project: Apache YuniKorn
> Issue Type: Sub-task
> Components: core - scheduler, scheduler-interface, shim - kubernetes
> Reporter: Wilfred Spiegelenburg
> Assignee: Kinga Marton
> Priority: Major
> Fix For: 0.10
>
>
> This is a small change in the SI which has a larger impact. The TerminationType can be reused for different actions. It is currently embedded in the AllocationRelease message.
> We should move it out of the message and make it a separate enumeration that can be used if we for instance terminate an asks or application.
> The flow on effect is in the core and shim as both use the value of this enumeration to decide if it needs to process the message. That means:
> # update SI
> # update the core dependency and code
> # update the shim dependencies and code
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: issues-help@yunikorn.apache.org