[
https://issues.apache.org/jira/browse/YUNIKORN-2526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17840222#comment-17840222
]
Shravan Achar commented on YUNIKORN-2526:
-----------------------------------------
This issue is when number of active pods go beyond the live heap, the scheduler
can get into a bad state. In this scenario, scheduler pod is at 4Gi and 12000
active pods were submitted to the clusters (across 7 applications with 1000
pods each)
> Discrepancy between shim cache and core app/task list after scheduler restart
> -----------------------------------------------------------------------------
>
> Key: YUNIKORN-2526
> URL: https://issues.apache.org/jira/browse/YUNIKORN-2526
> Project: Apache YuniKorn
> Issue Type: Bug
> Components: shim - kubernetes
> Reporter: Shravan Achar
> Priority: Major
> Attachments: log-snippet.txt, state-dump-4-1-3.json,
> state-dump-4-17.json.zip
>
>
> When scheduler restarts, occasionally it gets into a situation where the
> application is still in Running state despite the application getting
> terminated in the cluster. This is confirmed with the attached state dump.
>
> The scheduler core logs indicate all nodes are being evaluated for
> non-existing application (also attached). The CPU is being used up doing this
> unneeded evaluation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
