[FLINK-11716] Introduce Task Manager configuration option to customize address binding mechanism

• Type: Sub-task
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 1.8.0
• Labels: pull-request-available

Release Note

`TaskManagers` now bind to the host IP address instead of the hostname by default . This behaviour can be controlled by the configuration option `taskmanager.network.bind-policy`. If your Flink cluster should experience inexplicable connection problems after upgrading, try to set `taskmanager.network.bind-policy: name` in your `flink-conf.yaml` to return to the pre-1.8 behaviour.

• Assignee: Alex
• Reporter: Alex
• Created: 21/Feb/19 12:46
• Updated: 04/Mar/19 12:28
• Resolved: 25/Feb/19 10:41

Description

Proposed configuration (in flink-config.yaml):

taskmanager.network.bind-policy: name|ip

With the following behavior:

If a taskmanager.host configuration option set, then the new option has no effect. The provided address in the former would be used as binding address for TM.

Otherwise, TM would try to connect to a JM instance to determine it's binding address (java.net.InetAddress).
If taskmanager.network.bind-policy is:

• ip - (default) TM would use ip address of picked address (InetAddress.getHostAddress()). This is change in behavior compared with Flink 1.7 and earlier;
• name - TM would use name of the picked address (InetAddress.getHostName()). This is same as the old behavior, before introducing this feature.

Edit: updated after discussion with till.rohrmann and StephanEwen.

Issue Links

• links to: GitHub Pull Request #7795