[jira] [Resolved] (FLINK-11716) Introduce Task Manager configuration option to customize address binding mechanism

["Till Rohrmann (JIRA)" <ji...@apache.org>]

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

Till Rohrmann resolved FLINK-11716.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: 1.8.0

Fixed via 70107c4647ecac3df9b1b8c7920e7cb99ad550f1

> Introduce Task Manager configuration option to customize address binding mechanism
> ----------------------------------------------------------------------------------
>
>                 Key: FLINK-11716
>                 URL: https://issues.apache.org/jira/browse/FLINK-11716
>             Project: Flink
>          Issue Type: Sub-task
>            Reporter: Alex
>            Assignee: Alex
>            Priority: Minor
>              Labels: pull-request-available
>             Fix For: 1.8.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Proposed configuration (in {{flink-config.yaml}}):
> {code:java}
> network.taskmanager.bind-policy: name|ip
> {code}
> 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.host.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].



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)