[
https://issues.apache.org/jira/browse/FLINK-26605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17504935#comment-17504935
]
Gyula Fora commented on FLINK-26605:
------------------------------------
I think this also raises the question whether once in a READY state should we
periodically recheck (or everytime before reconcile) the state.
After we assume ready a simple rest call with a shorter timeout could be a
simple solution no?
> JobManagerDeploymentStatus.READY does not correctly reflect the real Flink
> cluster status
> -----------------------------------------------------------------------------------------
>
> Key: FLINK-26605
> URL: https://issues.apache.org/jira/browse/FLINK-26605
> Project: Flink
> Issue Type: Sub-task
> Components: Kubernetes Operator
> Reporter: Yang Wang
> Priority: Major
>
> Follow the discussion in the PR[1].
> {{JobManagerDeploymentStatus.READY}} does not mean the Flink cluster is ready
> for accepting REST API calls. This will cause problems when we are running
> session cluster.
> For example, if something is wrong or very slow with the leader election,
> {{JobManagerDeploymentStatus}} is {{READY}} but the session cluster is not
> ready for accepting job submission. What I mean is to update the
> {{JobManagerDeploymentStatus}} to {{READY}} only when the flink cluster is
> actually working.
>
> [1].
> https://github.com/apache/flink-kubernetes-operator/pull/51#discussion_r824359419
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
