[
https://issues.apache.org/jira/browse/FLINK-4424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15434777#comment-15434777
]
Till Rohrmann commented on FLINK-4424:
--------------------------------------
Yes that is the idea. It might actually make sense to create the
{{ConnectionManager}} and the {{NetworkBufferPool}} outside of the
{{NetworkEnvironment}} and then pass it to it via the constructor. We should
then also add a shutdown method to the {{NetworkEnvironment}} which will be
called when the {{TaskManager}} stops.
The changes have to be applied to the master and not the flip-6 branch. We'll
later cherry pick this commit to the feature branch.
> 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
>
> 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)
