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.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
