Previously, GROUP_BY would evenly assign instances to each group, keeping the groups within 1 instance count from each other. When placing 10 instances across three groups, Marathon would require 1 instance to placed in each group A, B and C before placing the 2nd instance, and so-on. With the change, Marathon will allow placing 4 instances in group A, even if no instances have been placed in B or C. This helps prevent prevent rolling deployments from becoming blocked when resources are used to near capacity, as the kill-order will not kill instances evenly across groups.
Previously, GROUP_BY would evenly assign instances to each group, keeping the groups within 1 instance count from each other. When placing 10 instances across three groups, Marathon would require 1 instance to placed in each group A, B and C before placing the 2nd instance, and so-on. With the change, Marathon will allow placing 4 instances in group A, even if no instances have been placed in B or C. This helps prevent prevent rolling deployments from becoming blocked when resources are used to near capacity, as the kill-order will not kill instances evenly across groups.
JIRA Issues: MARATHON-8752