flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "mingleizhang (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (FLINK-9537) JobManager isolation in session mode
Date Sat, 09 Jun 2018 11:10:00 GMT

     [ https://issues.apache.org/jira/browse/FLINK-9537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

mingleizhang reassigned FLINK-9537:

    Assignee:     (was: mingleizhang)

> JobManager isolation in session mode
> ------------------------------------
>                 Key: FLINK-9537
>                 URL: https://issues.apache.org/jira/browse/FLINK-9537
>             Project: Flink
>          Issue Type: Improvement
>          Components: Distributed Coordination
>    Affects Versions: 1.5.0, 1.6.0
>            Reporter: Till Rohrmann
>            Priority: Major
> Currently, all {{JobManagers}} are executed in the same process which also runs the {{Dispatcher}}
component when using the session mode. This is problematic, since the {{JobManager}} also
executes user code. Consequently, a bug in a single Flink job can cause the failure of the
other {{JobManagers}} running in the same process. In order to avoid this we should add the
functionality to run each {{JobManager}} in its own process.

This message was sent by Atlassian JIRA

View raw message