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/04 09:03:00 UTC
[jira] [Comment Edited] (YUNIKORN-538) Scheduler is unable to
recovery from a restart
[ https://issues.apache.org/jira/browse/YUNIKORN-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17278676#comment-17278676 ]
Kinga Marton edited comment on YUNIKORN-538 at 2/4/21, 9:02 AM:
----------------------------------------------------------------
Thanks [~wwei]! I tested your changes and it solves the recovery issue: both the nodes and the applications are recovered as expected. Also the applications will have the correct state after recovery, *but* the queue name is not filled.
was (Author: kmarton):
Thanks [~wwei]! I tested your changes and it solves the recovery issue: both the nodes and the applications are recovered as expected. Also the applications will have the correct state after recovery.
> 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: Sub-task
> Components: shim - kubernetes
> Reporter: Kinga Marton
> Assignee: Weiwei Yang
> Priority: Blocker
> Labels: pull-request-available
>
> 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: issues-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: issues-help@yunikorn.apache.org