You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Till Rohrmann (Jira)" <ji...@apache.org> on 2020/04/03 11:20:00 UTC
[jira] [Resolved] (FLINK-16705) LocalExecutor tears down
MiniCluster before client can retrieve JobResult
[ https://issues.apache.org/jira/browse/FLINK-16705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Till Rohrmann resolved FLINK-16705.
-----------------------------------
Resolution: Fixed
Fixed via
1.11.0: db81417b8616850aa36b34fecafcc275db2cb10a
1.10.1: 128f5f7bd1da9ae50973115b38f4def3adc331e1
> 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
> Affects Versions: 1.10.0
> Reporter: Maximilian Michels
> Assignee: Maximilian Michels
> Priority: Blocker
> Labels: pull-request-available
> Fix For: 1.10.1, 1.11.0
>
> Time Spent: 20m
> 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)