You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flink.apache.org by "Till Rohrmann (JIRA)" <ji...@apache.org> on 2016/11/16 17:33:58 UTC
[jira] [Created] (FLINK-5082) Pull ExecutionService lifecycle
management out of the JobManager
Till Rohrmann created FLINK-5082:
------------------------------------
Summary: 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.1.3, 1.2.0
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)