Details

      Description

      via slack: https://mesosphere.slack.com/archives/C1U6FPSTT/p1490885493176471

      pretty sure that our constraint validation for CLUSTER is buggy: constraint value isn't required when the field is `hostname`:
      https://github.com/mesosphere/marathon/blob/5495479035facdcca05d6b58c6c09a0413c02c34/src/main/scala/mesosphere/mesos/Constraints.scala#L98
      docs say (incorrectly): https://github.com/mesosphere/marathon/blob/master/docs/docs/constraints.md#cluster-operator
      validation rule says (incorrectly): https://github.com/mesosphere/marathon/blob/17796e25b4a3723f0ebbf094e982dbe6e15c2f5b/src/main/scala/mesosphere/marathon/state/AppDefinition.scala#L536
      ^^^ i'll file a ticket (and we should probably backport this to releases/1.4)

      pretty sure that the intent is to support `[hostname, CLUSTER]`

      looks like the above syntax says "launched instances have affinity for each other" (as long as an instance is running, additional instances will launch on the same host)

      Impacts all releases post-1.1

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                jdef James DeFelice
                Reporter:
                jdef James DeFelice
                Team:
                Orchestration Team
                Watchers:
                James DeFelice
              • Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: