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 <taskmanager_pod> --previous` to check the logs. Best, Yang David Morávek <d...@apache.org> 于2021年7月22日周四 下午8:04写道： > 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 <fabianp...@ververica.com> > wrote: > >> CC user ML >> >>
