Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.3.0
    • Component/s: Cluster Management, Mesos
    • Labels:
      None

      Description

      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.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                vijikarthi Vijay Srinivasaraghavan
                Reporter:
                eronwright Eron Wright
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: