Uploaded image for project: 'Marathon'
  1. Marathon
  2. MARATHON-3251

Marathon scheduler default binding

    Details

    • Type: Task
    • Status: Resolved
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:

      Description

      Marathon scheduler binding uses the following hierarchy:

      machine hostname resolvable -> marathon binding to resolved address
      machine hostname resolvable, LIBPROCESS_IP set in env -> marathon binding to resolved address
      machine hostname not resolvable, LIBPROCESS_IP set in env -> marathon binding to LIBPROCESS_IP
      machine hostname not resolvable, LIBPROCESS_IP not set in env -> marathon binding to nothing

      A reasonable default (e.g. 127.0.0.1) would be helpful in the last case so that marathon starts in each case.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              mroth Michael Roth (Inactive)
              Team:
              Orchestration Team
              Watchers:
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: