[
https://issues.apache.org/jira/browse/FLINK-26370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17501126#comment-17501126
]
Yang Wang commented on FLINK-26370:
-----------------------------------
I am thinking do we really need to get the job status for every reconciliation.
[~gyfora] Do you have any concerns if we have a background-updated job status
cache?
I ask this question again because manual savepoint is in a similar situation[1]
and users are hard to configure the thread pool size.
[1].
https://github.com/apache/flink-kubernetes-operator/pull/38#pullrequestreview-899750005
> Make Flink cluster communication asynchronous
> ---------------------------------------------
>
> Key: FLINK-26370
> URL: https://issues.apache.org/jira/browse/FLINK-26370
> Project: Flink
> Issue Type: Sub-task
> Components: Kubernetes Operator
> Reporter: Gyula Fora
> Assignee: Sandor Kelemen
> Priority: Major
>
> In the current architecture calls to the flink clusters (through the rest
> client) are made synchronously from the reconcile loop.
> These calls often take a long time due to various (compeltely normal) reasons:
> - Cluster is not ready -> long call + timeoutexception
> - Operation takes a long time -> cancel/savepoint operations are often
> expected to take seconds/minutes
> Both the observer and reconciler components make these calls.
> We should come up with a way to avoid making these sync calls from the main
> loop while still preserving the logic of the operator.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
