[
https://issues.apache.org/jira/browse/YUNIKORN-408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17193890#comment-17193890
]
Weiwei Yang commented on YUNIKORN-408:
--------------------------------------
Hi [~vbm], thanks for raising this up.
[~adam.antal], could you please take a look at this issue? I just took a quick
look, the DEBUG message "pod is not added to scheduler cache, so cannot be
updated" doesn't seem to be something needs to be worried about. Looks like we
got an Update pod event but the pod has already been removed from the cluster
(the description mentioned the pod deletion as well).
I can't remember all the logic now, are the metrics showing up here the
accumulated counts of apps/containers or instant numbers?
> Result mismatch between Container_Status and Container_History
> --------------------------------------------------------------
>
> Key: YUNIKORN-408
> URL: https://issues.apache.org/jira/browse/YUNIKORN-408
> Project: Apache YuniKorn
> Issue Type: Bug
> Components: webapp
> Reporter: Vishwas
> Assignee: Adam Antal
> Priority: Major
> Attachments: appStatus_vs_contStatus.PNG, scheduler.log
>
>
> I have created a single pod to use the yunikorn scheduler and it gets
> allocated properly to the queue.
> When I delete the pod using the kubectl delete comand, I still see the
> container count as 1 in container_history but number of running container as
> 0 and also in application status I see it is running.
> I see below log in scheduler, not sure if it is related:
> {code:java}
> 2020-09-10T08:43:41.895Z DEBUG cache/context.go:241 failed to
> update pod in cache {"podName": "app-sleep-0", "error": "pod
> e9a531a8-e001-4cc9-bd3e-2d63852eacd7 is not added to scheduler cache, so
> cannot be updated"}{code}
> I have attached the snapshot of the UI and the scheduler.log from pod.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
