David's suggestion makes a lot of sense. You need to check whether the
TaskManager is killed by Kubernetes via `kubectl describe pod` for exit
code or the kubelet logs.
If it is not killed by Kubernetes, then it might crashed internally. Please
use `kubectl logs --previous` to check the logs.
Be
If you run `kubectl describe pod ...` on the affected pod, you should see a
reason why the previous pod has terminated (eg. OOM killed by Kubernetes).
Best,
D.
On Thu, Jul 22, 2021 at 9:30 AM Fabian Paul
wrote:
> CC user ML
>
>
CC user ML
Hi Flink Community,
Recently I deployed a Flink cluster(1 JM, 1TM) with k8s standalone mode. Later
on I notice that the pod which the TM is running on got restarted by k8s very
frequently (3 times within 10 minutes). And I didn't see any error log for
this pod. I tried to increase the containe
