[
https://issues.apache.org/jira/browse/FLINK-26473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17501185#comment-17501185
]
Nicholas Jiang edited comment on FLINK-26473 at 3/4/22, 6:48 AM:
-----------------------------------------------------------------
[~wangyang0918], is the point above mentioned that the observer should check
the job state of the deployment for covering scenarios like crash etc where the
JobManagerDeploymentStatus comes to READY?
was (Author: nicholasjiang):
[~wangyang0918], do you mean that the observer should check the job state of
the deployment for above scenarios where the JobManagerDeploymentStatus comes
to READY?
> Observer should support JobManager deployment crashed or deleted externally
> ---------------------------------------------------------------------------
>
> Key: FLINK-26473
> URL: https://issues.apache.org/jira/browse/FLINK-26473
> Project: Flink
> Issue Type: Sub-task
> Components: Kubernetes Operator
> Reporter: Yang Wang
> Priority: Major
>
> Follow the discussion in this PR
> [https://github.com/apache/flink-kubernetes-operator/pull/26#discussion_r817514763.]
>
> Currently, the {{observeJmDeployment}} still could not cover some scenarios,
> e.g. JobManager deployment crashed, JobManager deployment was deleted
> externally. When it {{JobManagerDeploymentStatus}} comes to {{{}READY{}}}, it
> will always be {{{}READY{}}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
