[
https://issues.apache.org/jira/browse/YUNIKORN-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17080189#comment-17080189
]
Tao Yang commented on YUNIKORN-84:
----------------------------------
Hi, [~wilfreds]. Thanks for the review and feedback.
I have met this issue in a kubemark cluster which has been updated for many
times, it can't be reproduced any more but I can remember the error was "failed
to find application ..." for kube-system pods like etcd, apiserver etc. I
didn't dig this error in time and it just gone later, maybe it's caused by
abnormal things in the test environment, so I'm not sure if we should take any
further action on this error. However, what we can do now is to guarantee that
all final states of nodes should be counted into nodesRecovered.
> Always waiting in recovery phase as long as rejected node exists
> ----------------------------------------------------------------
>
> Key: YUNIKORN-84
> URL: https://issues.apache.org/jira/browse/YUNIKORN-84
> Project: Apache YuniKorn
> Issue Type: Bug
> Reporter: Tao Yang
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In recovery phase, scheduler keeps waiting until all nodes are recovered, but
> not all nodes are considered according to Context#recover in
> context_recovery.go, only nodes with Healthy or Draining state will be
> counted, nodes with Rejected state should be counted as well.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]