flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Till Rohrmann (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (FLINK-4424) Make network environment start-up/shutdown independent of JobManager association
Date Fri, 02 Sep 2016 13:07:20 GMT

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

Till Rohrmann closed FLINK-4424.
--------------------------------
    Resolution: Fixed

Fixed via 78f2a15867734055a9712ea3a27f54d9bed3e43b

> Make network environment start-up/shutdown independent of JobManager association
> --------------------------------------------------------------------------------
>
>                 Key: FLINK-4424
>                 URL: https://issues.apache.org/jira/browse/FLINK-4424
>             Project: Flink
>          Issue Type: Improvement
>          Components: Network, TaskManager
>            Reporter: Till Rohrmann
>            Assignee: Till Rohrmann
>
> Currently, the {{TaskManager}} starts the netty network server only after it has registered
with a {{JobManager}}. Upon loss of connection to the {{JobManager}} the {{NetworkEnvironment}}
is closed.
> The start-up and shutdown of the network server should be independent of the {{JobManager}}
connection, especially if we assume that a TM can be associated with multiple JobManagers
in the future (FLIP-6).
> Starting the network server only once when the {{TaskManager}} is started has the advantage
that we don't have to preconfigure the {{TaskManager's}} data port. Furthermore we don't risk
to get stuck when disassociating from a {{JobManager}} because the start-up and shutdown of
a {{NetworkEnvironment}} can cause problems (because it has to reserve/free resources).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message