the JM's main contain has been successfully shut down by the REST API, then it
was restarted by the restart policy, because the pod was still not deleted.
That's why we observed `Jobmanager restart after it has been requested to stop`
发件人: Yang Wang
发送时
If you could find the "Deregistering Flink Kubernetes cluster, clusterId"
in the JobManager log, then it is not the expected behavior.
Having the full logs of JobManager Pod before restarted will help a lot.
Best,
Yang
On Fri, Feb 2, 2024 at 1:26 PM Liting Liu (litiliu) via user <
user@flink.a
Hi, community:
I'm running a Flink 1.14.3 job with flink-Kubernetes-operator-1.6.0 on
the AWS. I found my flink jobmananger container's thread restarted after this
flinkdeployment has been requested to stop, here is the log of jobmanager:
2024-02-01 21:57:48,977 tn="flink-akka.actor.defaul
