[
https://issues.apache.org/jira/browse/FLINK-5974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15995000#comment-15995000
]
ASF GitHub Bot commented on FLINK-5974:
---------------------------------------
Github user tillrohrmann commented on the issue:
https://github.com/apache/flink/pull/3692
Why do we actually make `TaskManager` hostname configurable via
`mesos.resourcemanager.tasks.hostname`? Isn't the mesos-dns hostname already
uniquely defined by the `TaskID` and the framework name contained in
`FrameworkInfo`?
If the `FrameworkInfo` does not contain the service name, then we should
only specify this information. Then we could rename the configuration parameter
into `mesos.service-name` and concatenate `taskId`, `service-name` and `mesos`,
where `taskId` is retrieved from the `TaskID` instance.
> 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
>
> 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)
