You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Eron Wright (JIRA)" <ji...@apache.org> on 2017/03/06 20:01:32 UTC

[jira] [Created] (FLINK-5974) Support Mesos DNS

Eron Wright  created FLINK-5974:
-----------------------------------

             Summary: Support Mesos DNS
                 Key: FLINK-5974
                 URL: https://issues.apache.org/jira/browse/FLINK-5974
             Project: Flink
          Issue Type: Improvement
          Components: Cluster Management, Mesos
            Reporter: Eron Wright 
            Assignee: Eron Wright 



In certain Mesos/DCOS environments, the slave hostnames aren't resolvable.  For this and other reasons, Mesos DNS names would ideally be used for communication within the Flink cluster, not the hostname discovered via `InetAddress.getLocalHost`.

Some parts of Flink are already configurable in this respect, notably `jobmanager.rpc.address`.  However, the Mesos AppMaster doesn't use that setting for non-JM addresses (e.g. artifact server), it uses the hostname.

Similarly, the `taskmanager.hostname` setting isn't used in Mesos deployment mode.   To effectively use Mesos DNS, the TM should use `<task-name>.<framework-name>.mesos` as its hostname.   This could be derived from an interpolate configuration string.





--
This message was sent by Atlassian JIRA
(v6.3.15#6346)