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

Add clarification that adding or changing --mesos_role parameter value changes existing role registration since Mesos 1.3.

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Medium
    • Resolution: Done
    • Affects Version/s: Marathon 1.6.535
    • Fix Version/s: DC/OS 1.12.0
    • Component/s: Docs
    • Labels:
      None

      Description

      Current documentation states:

      --mesos_role (Optional. Default: None): Mesos role for this framework. If set, Marathon receives resource offers for the specified role in addition to resources with the role designation ‘*’. This parameter is only applied the first time the framework registers with Mesos. If you change this parameter to another value later, or leave it out, this will not have an effect on the role for which Marathon is registered. Please note that Marathon currently supports only one Mesos role, support for multiple roles will be added in the future releases.
      

      The part about being unable to change the role is no longer the case since Mesos 1.3, and is misleading.  It would be better to point out that this is legacy behavior.

      Relevant ticket: https://jira.mesosphere.com/browse/MARATHON-7359

        Attachments

          Activity

            People

            • Assignee:
              nikitamelkozerov Nikita Melkozerov
              Reporter:
              lishim lishim
              Team:
              Orchestration Team
              Watchers:
              lishim
            • Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: