[
https://issues.apache.org/jira/browse/FLINK-5082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Till Rohrmann closed FLINK-5082.
--------------------------------
Resolution: Fixed
Fixed in 1.2 via ae4b274a9919d01a236df4e819a0a07c5d8543ac
Fixed in 1.1.4 via 7fb71c5bf1aab85250bf29bd0ea0654079cea48f
> Pull ExecutionService lifecycle management out of the JobManager
> ----------------------------------------------------------------
>
> Key: FLINK-5082
> URL: https://issues.apache.org/jira/browse/FLINK-5082
> Project: Flink
> Issue Type: Bug
> Components: JobManager
> Affects Versions: 1.2.0, 1.1.3
> Reporter: Till Rohrmann
> Assignee: Till Rohrmann
> Fix For: 1.2.0, 1.1.4
>
>
> The {{JobManager}} receives an {{ExecutorService}} to run its futures as a
> constructor parameter. Even though the {{ExecutorService}} comes from
> outside, the {{JobManager}} shuts the executor service down if the
> {{JobManager}} terminates. This is clearly a sub-optimal behaviour leading
> also to {{RejectedExecutionExceptions}}.
> I propose to move the {{ExecutorService}} lifecycle management out of the
> {{JobManager}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
