Thanks, Till.
Currently, the instance is getting timeout error and terminating the
TaskManager.
Sure, will try native K8s.
On Thu, Aug 13, 2020 at 3:12 PM Till Rohrmann wrote:
> Hi Narasimha,
>
> if you are deploying the Flink cluster manually on K8s then there is
> no automatic way of stoppin
Hi Narasimha,
if you are deploying the Flink cluster manually on K8s then there is
no automatic way of stopping the TaskExecutor/TaskManager pods. This is
something you have to do manually (similar to a standalone deployment). The
only clean up mechanism is the automatic termination of the TaskMan
Hi Narasimha,
I am not sure why the TMs are not shutting down, as Yun said, so I am
cc'ing Till here as he may be able to shed some light.
For the application mode, the page in the documentation that you
pointed is the recommended way to deploy an application in application
mode.
Cheers,
Kostas
Thanks, Yun for the prompt reply.
TaskManager was actively looking for ResourceManager, on timeout of 5 mins
it got terminated.
Any recommendations around this? Or is this the way this will work.
What should be done around this to make the application start in
application deployment mode?
https
Hi
>From your description, the task managers are still alive even the job is
>finished and job manager has shut down?
If so, I think this is really weird, could you check what the TM is doing via
jstack and the logs in job manager and idle task manager?
The task manager should be released when t
