[
https://issues.apache.org/jira/browse/FLINK-16705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17063916#comment-17063916
]
Zili Chen commented on FLINK-16705:
-----------------------------------
Ref
https://github.com/apache/flink/commit/c927e176f35b9db0f9daec7b67ccdb41d8e7d9f5
https://github.com/apache/flink/commit/41176ba0189ef2782449a1b7d4d074adc8a4af6f
> 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
> 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)
