Thank you for timely help!
I've tried session mode a little bit, it's better than I thought, the
TaskManager can be allocated and de-allocated dynamically. But it seems the
memory size of TaskManager is fixed when the session starts, and can not be
adjusted for different job.
I'll try to deploy
There are two ways to access the status of a job after it is finished.
1. You can try native k8s deployment in session mode. When jobs are
finished in this mode, TMs will be automatically released after a
short period of time, while JM will not be terminated until you explicitly
shutdown the
Hi,
We are currently using Flink 1.6 standalone mode, but the lack of
isolation is a headache for us. At present, I am trying application mode
of Flink 1.13.0 on native K8s.
I found that as soon as the job ends, whether it ends normally or
abnormally, the jobmanager can no longer be accessed,
