Details
-
Sub-task
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
Description
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.
Another case is even though JobManager crashed backoff, the JobManagerDeploymentStatus is still READY.
[1]. https://github.com/apache/flink-kubernetes-operator/pull/51#discussion_r824359419
Attachments
Issue Links
- links to