We observed that Aurora's CPU share in Mesos Master dashboard spikes upto 100%, even when Aurora is not running any Job. Looking at the code, I figured that scheduler holds on to the resourceOffers, even if there are no tasks to be scheduled and doesn't decline the offer immediately.
It looks like an optimization, where the TaskLaunchers are kept primed with resourceOffers, so that the Job can be run as soon as it's scheduled (if task requirements are satisfied). But, this leads to an offer starvation problem for other peer frameworks who tend to decline offers if they don't have tasks to be scheduled (for the timeout period). How can we handle this in scenarios where Aurora is running with other peer frameworks ? Thanks Mohit
