flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-5082) Pull ExecutionService lifecycle management out of the JobManager
Date Tue, 22 Nov 2016 22:11:58 GMT

    [ https://issues.apache.org/jira/browse/FLINK-5082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15688071#comment-15688071
] 

ASF GitHub Bot commented on FLINK-5082:
---------------------------------------

Github user asfgit closed the pull request at:

    https://github.com/apache/flink/pull/2820


> 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)

Mime
View raw message