[
https://issues.apache.org/jira/browse/YUNIKORN-561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Weiwei Yang updated YUNIKORN-561:
---------------------------------
Description:
During restart, we are missing to add some allocationTags:
Pre-restart:
"allocationTags": {
"kubernetes.io/label/app": "sleep",
"kubernetes.io/label/applicationId": "runnable",
"kubernetes.io/meta/namespace": "dev",
"kubernetes.io/meta/podName": "runnable-1"
},
Post-restart:
"allocationTags": {
"namespace": "dev"
},
this is due to that YUNIKORN-55 did not consider the recovery case.
was:
In YUNIKORN-54, we simplify the way to generate application IDs. The side
effect is when we look at info from web UI, we lose some info about the pod
info such as pod name, namespace, etc.
A proper way to handle this is to get this info from pod and add labels,
annotations info to allocation ask as attributes, and then send to
scheduler-core. Also on web rest API, we need to display these attributes too.
> Some container tags are missing upon scheduler restart
> ------------------------------------------------------
>
> Key: YUNIKORN-561
> URL: https://issues.apache.org/jira/browse/YUNIKORN-561
> Project: Apache YuniKorn
> Issue Type: Bug
> Components: core - scheduler, shim - kubernetes, webapp
> Reporter: Weiwei Yang
> Assignee: Adam Antal
> Priority: Major
> Labels: pull-request-available
> Fix For: 0.9
>
>
> During restart, we are missing to add some allocationTags:
> Pre-restart:
> "allocationTags": {
> "kubernetes.io/label/app": "sleep",
> "kubernetes.io/label/applicationId": "runnable",
> "kubernetes.io/meta/namespace": "dev",
> "kubernetes.io/meta/podName": "runnable-1"
> },
> Post-restart:
> "allocationTags": {
> "namespace": "dev"
> },
> this is due to that YUNIKORN-55 did not consider the recovery case.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]