[
https://issues.apache.org/jira/browse/YUNIKORN-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17278444#comment-17278444
]
Weiwei Yang commented on YUNIKORN-538:
--------------------------------------
Hi [~kmarton] I am taking this over as I found the same issue.
I can reproduce the recovery failure, due to timeout after a restart. This is a
regression after YUNIKORN-2. Adding to the umbrella.
> Scheduler is unable to recovery from a restart
> -----------------------------------------------
>
> Key: YUNIKORN-538
> URL: https://issues.apache.org/jira/browse/YUNIKORN-538
> Project: Apache YuniKorn
> Issue Type: Bug
> Components: shim - kubernetes
> Reporter: Kinga Marton
> Assignee: Weiwei Yang
> Priority: Major
>
> After the changes made in YUNIKORN-518 node recovery is broken.
> Actually, the nodes are not recovered. The first commit when the issue is
> observed is the following one:
> [https://github.com/apache/incubator-yunikorn-k8shim/commit/4d0b887cb13619247503544d7f4e5c1672b6f291]
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
