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://ci.apache.org/projects/flink/flink-docs-release-1.11/ops/deployment/native_kubernetes.html#start-flink-application Here it has shown to invoke Flink binary to start. Is this the preferred way? On Mon, Aug 10, 2020 at 1:46 PM Yun Tang <myas...@live.com> wrote: > 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 the JM is shutting down. > Moreover, idle task manager would also release after 30 seconds by default > [1]. > > > [1] > https://ci.apache.org/projects/flink/flink-docs-stable/ops/config.html#resourcemanager-taskmanager-timeout > > Best > Yun Tang > > > ------------------------------ > *From:* narasimha <swamy.haj...@gmail.com> > *Sent:* Monday, August 10, 2020 15:36 > *To:* user@flink.apache.org <user@flink.apache.org> > *Subject:* TaskManagers are still up even after job execution completed > in PerJob deployment mode > > > I'm trying out Flink Per-Job deployment using docker-compose. > > Configurations: > > version: "2.2" > jobs: > jobmanager: > build: ./ > image: flink_local:1.1 > ports: > - "8081:8081" > command: standalone-job --job-classname com.organization.BatchJob > environment: > - | > FLINK_PROPERTIES= > jobmanager.rpc.address: jobmanager > parallelism.default: 2 > taskmanager: > image: flink_local:1.1 > depends_on: > - jobmanager > command: taskmanager > scale: 1 > environment: > - | > FLINK_PROPERTIES= > jobmanager.rpc.address: jobmanager > taskmanager.numberOfTaskSlots: 2 > parallelism.default: 2 > > Flink image is extended with job.jar, Job executed successfully. > > JobManager exited after the job is completed, but is still running, which > is not expected. > > Any configurations have to be added to exit both JobManager and TaskManger > ? > > Versions: > > Flink - 1.11.0 > > Java - 1.8 > > -- > A.Narasimha Swamy > > -- A.Narasimha Swamy
