Details
-
Sub-task
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
Description
Currently, JobClient is AutoCloseable and we require users to close the JobClient that they get as a result from executeAsync(). This is problematic because users can simply ignore the result of executeAsync() and then we will leak the resources that the client has.
We should change the JobClient so that it acquires the required ClusterClient for each method call and closes it again.
This means that the users no longer have the burden of managing the JobClient lifecycle, i.e. they can freely ignore the result of executeAsync().
Attachments
Issue Links
- causes
-
FLINK-18959 Fail to archiveExecutionGraph because job is not finished when dispatcher close
- Closed
-
FLINK-16637 Flink per job mode terminates before serving job cancellation result
- Closed
- is related to
-
FLINK-14992 Add job submission listener to execution environments
- Closed
- links to