flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-5974) Support Mesos DNS
Date Wed, 03 May 2017 15:43:04 GMT

    [ https://issues.apache.org/jira/browse/FLINK-5974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15995099#comment-15995099

ASF GitHub Bot commented on FLINK-5974:

Github user EronWright commented on the issue:

    @tillrohrmann Mesos DNS is not the only DNS solution for Mesos, it is merely the DCOS
solution.  By using an interpolated string, the name is fully configurable.

> 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

View raw message