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

Misleading Marathon constraint operators documentation for Mesos attributes of ranges

    Details

      Description

      The documentation for Marathon constraints do not clearly explain to users how Marathon "supports" range attribute types. For instance, if a Mesos agent has attr:[1-10], and the Marathon app constraint is attr:CLUSTER:2, the constraint won't be ever satisfied because the way the constraint matching works on the Marathon side is all attributes received from Mesos are converted to strings first, and then strings used for matching. In this particular case, "[1-10]" is literally compared with "2".

      http://mesos.apache.org/documentation/latest/attributes-resources/

      Acceptance criteria

      As a user
      When I read the Marathon constraints documentation
      Then I should understand that LIKE, UNLIKE, UNIQUE, and CLUSTER, MAX_PER and GROUP_BY treat Mesos range attributes as text
      And also I should not be given the impression that Marathon does anything with Mesos set attributes (they don't exist)

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                matthias.eichstedt Matthias Eichstedt
                Reporter:
                ivanchernetsky Ivan Chernetsky
                Team:
                Orchestration Team
                Watchers:
                Ivan Chernetsky, Matthias Eichstedt, Philip Norman, Tim Harper
              • Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated: