Yaron, You could use the /statistics.json endpoints to monitor the cpu/memory allocation across your cluster, even on individual nodes. Only individual frameworks know their own pending tasks and how many additional resources you would need to satisfy them. Given these pieces of information, you should be able to trigger your own auto-provisioning mechanism.
On Fri, May 1, 2015 at 11:18 AM, Yaron Rosenbaum <[email protected]> wrote: > Hi > > Is there a way in mesos / marathon to know that tasks cannot be assigned > due to lack of resources? or in other words - when to add mesos-slaves to > the cluster? > > Or even more specifically, what amount of resources are missing (or in > excess) given the current tasks and slaves? > > Thanks > (Y) > >
