You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@yunikorn.apache.org by "Chaoran Yu (Jira)" <ji...@apache.org> on 2021/05/19 16:06:00 UTC
[jira] [Created] (YUNIKORN-675) Pod status update could fail due to
conflicts
Chaoran Yu created YUNIKORN-675:
-----------------------------------
Summary: Pod status update could fail due to conflicts
Key: YUNIKORN-675
URL: https://issues.apache.org/jira/browse/YUNIKORN-675
Project: Apache YuniKorn
Issue Type: Bug
Components: shim - kubernetes
Reporter: Chaoran Yu
Assignee: Chaoran Yu
https://issues.apache.org/jira/browse/YUNIKORN-657 introduced a change that set the pods to failed status when there's an application scheduling error. But the update of pod status may occasionally fail due to conflicts (e.g. the pods have been modified elsewhere). Need to get the latest pod before applying the status update. Also retry with exponential backoff if conflicts still exist
--
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