Affects Version/s: None
Fix Version/s: None
The original message is reproduced below:
> I created X number of instances to launch with the app and mesos could
> only schedule Y where Y < X because of resource scarcity. I guess
> marathon cannot launch any more because mesos would not provide any
> resource offers.
> It would be good to get that data point from marathon that instead of
> the requested, less instances are launched. One can count the
> individual instances to get that info but though for larger
> deployments quickly seeing a mismatch would help to trigger say more
> resource addition or free up other resources as a corrective action
> from a monitoring system.