[
https://issues.apache.org/jira/browse/YUNIKORN-560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17300205#comment-17300205
]
Kinga Marton edited comment on YUNIKORN-560 at 3/12/21, 10:30 AM:
------------------------------------------------------------------
One of the approaches being considered is to use owner reference to fix the
issue, but we cannot use the owner reference cross namespace, so we need to
find some other solution.
Since the fix is not as straight forward as just set some owner reference, and
we need to discuss the possible solutions I would move this out from the scope
or 0.10 release.
was (Author: kmarton):
One of the approaches being considered is to use owner reference to fix the
issue, but we cannot use the owner reference cross namespace, so we need to
find some other solution.
Since the fix is not as straight forward as just set some owner reference, and
we need to discuss the possible solutions I am going to move this out from the
scope or 0.10 release.
> Yunikorn recovery deletes existing placeholders
> -----------------------------------------------
>
> Key: YUNIKORN-560
> URL: https://issues.apache.org/jira/browse/YUNIKORN-560
> Project: Apache YuniKorn
> Issue Type: Sub-task
> Components: shim - kubernetes
> Reporter: Kinga Marton
> Assignee: Kinga Marton
> Priority: Major
>
> On recovery, Yunikorn may intermittently delete placeholder pods. To
> reproduce, submit a gang job with minMembers > job parallelism (to guarantee
> that there are some placeholders running) and then delete yunikorn scheduler
> pod.
> After recovery, there may not be any placeholder pods remaining.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: issues-h...@yunikorn.apache.org
