You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Aljoscha Krettek (Jira)" <ji...@apache.org> on 2019/12/06 18:20:00 UTC
[jira] [Commented] (FLINK-15116) Make JobClient stateless, remove
AutoCloseable
[ https://issues.apache.org/jira/browse/FLINK-15116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16990056#comment-16990056 ]
Aljoscha Krettek commented on FLINK-15116:
------------------------------------------
If the {{JobClient}} is stateless FLINK-14992 becomes easier because we can just always pass a {{JobClient}} to the {{JobListener}} and not care about the lifecycle.
> Make JobClient stateless, remove AutoCloseable
> ----------------------------------------------
>
> Key: FLINK-15116
> URL: https://issues.apache.org/jira/browse/FLINK-15116
> Project: Flink
> Issue Type: Sub-task
> Components: API / DataSet, API / DataStream
> Reporter: Aljoscha Krettek
> Assignee: Aljoscha Krettek
> Priority: Major
>
> 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().
--
This message was sent by Atlassian Jira
(v8.3.4#803005)