[
https://issues.apache.org/jira/browse/FLINK-16705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17063927#comment-17063927
]
Maximilian Michels commented on FLINK-16705:
--------------------------------------------
Hi [~tison]. Not sure if you saw the PR already. I've opened it shortly after
opening this issue. I went for a per-job mini cluster client which handles the
shutdown and caches the result. This seemed like the best solution to me and
avoids altering any of the JobClient logic.
> LocalExecutor tears down MiniCluster before client can retrieve JobResult
> -------------------------------------------------------------------------
>
> Key: FLINK-16705
> URL: https://issues.apache.org/jira/browse/FLINK-16705
> Project: Flink
> Issue Type: Bug
> Components: Client / Job Submission
> Reporter: Maximilian Michels
> Assignee: Maximilian Michels
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.10.1
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> There is a race condition in {{LocalExecutor}} between (a) shutting down the
> cluster when the job has finished and (b) the client which retrieves the
> result of the job execution.
> This was observed in Beam, running a large test suite with the Flink Runner.
> We should make sure the job result retrieval and the cluster shutdown do not
> interfere.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
