You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Alex (JIRA)" <ji...@apache.org> on 2019/02/21 12:47:00 UTC

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

Alex created FLINK-11716:
----------------------------

             Summary: 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


Proposed configuration (in {{flink-config.yaml}}):
{code}
taskmanager.host.bind-policy: hostname|ip|auto-detect-hostname
{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, if {{taskmanager.host.bind-policy}} is:
    * {{auto-detect-hostname}} - (default, same as current behavior) TM would try to connect to a JM instance to determine it's binding address name;
    *  {{hostname}} - TM would use host's hostname as binding address ({{InetAddress.getLocalHost().getHostName()}});
    * {{ip}} - TM would use host's ip address as binding address ({{InetAddress.getLocalHost().getHostAddress()}}).



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