[
https://issues.apache.org/jira/browse/YUNIKORN-675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Weiwei Yang resolved YUNIKORN-675.
----------------------------------
Fix Version/s: 0.11
Resolution: Fixed
> 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
> Priority: Minor
> Fix For: 0.11
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
