You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/05/03 13:51:04 UTC
[jira] [Commented] (FLINK-5974) Support Mesos DNS
[ https://issues.apache.org/jira/browse/FLINK-5974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15994915#comment-15994915 ]
ASF GitHub Bot commented on FLINK-5974:
---------------------------------------
Github user tillrohrmann commented on the issue:
https://github.com/apache/flink/pull/3692
Thanks for your contribution @vijikarthi and @EronWright and @StephanEwen for the review work. I will address @StephanEwen's comments and then merge this PR.
> 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)