[
https://issues.apache.org/jira/browse/FLINK-27551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17533656#comment-17533656
]
Matyas Orhidi commented on FLINK-27551:
---------------------------------------
Just thinking out loud:Â Retrying status updates in case of a version conflict
makes no sense, it'll never succeed. We should probably just let the current
status update go and wait another reconcile loop to deal with it.
> Consider implementing our own status update logic
> -------------------------------------------------
>
> Key: FLINK-27551
> URL: https://issues.apache.org/jira/browse/FLINK-27551
> Project: Flink
> Issue Type: Improvement
> Components: Kubernetes Operator
> Reporter: Gyula Fora
> Priority: Critical
>
> If a custom resource version is applied while in the middle of a reconcile
> loop (for the same resource but previous version) the status update will
> throw an error and re-trigger reconciliation.
> In our case this might be problematic as it would mean we would retry
> operations that are not necessarily retriable and might require manual user
> intervention.
> Please see:
> [https://github.com/java-operator-sdk/java-operator-sdk/issues/1198]
> I think we should consider implementing our own status update logic that is
> independent of the current resource version to make the flow more robust.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
