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

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

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

Till Rohrmann resolved FLINK-5974.
----------------------------------
       Resolution: Fixed
    Fix Version/s: 1.3.0

Added via d7364fffbf552aed79e537a7aec3af593cb4e159

> 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: Vijay Srinivasaraghavan
>             Fix For: 1.3.0
>
>
> 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 everything (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 interpolated configuration string.



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