[FLINK-4424] Make network environment start-up/shutdown independent of JobManager association

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Component/s: Runtime / Coordination, Runtime / Network
• Assignee: Till Rohrmann
• Reporter: Till Rohrmann
• Created: 18/Aug/16 12:32
• Updated: 29/Jan/17 14:42
• Resolved: 02/Sep/16 13:06

Description

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

Issue Links

• blocks: FLINK-4458 Remove ForkableFlinkMiniCluster
• is depended upon by: FLINK-4343 Implement new TaskManager
• is related to: FLINK-4455 Replace ActorGateways in NetworkEnvironment by interfaces