There is also a /v2/queue endpoint in Marathon to inspect tasks that have been released, but not yet scheduled. -- Connor
> On May 7, 2015, at 01:07, Adam Bordelon <[email protected]> wrote: > > Yaron, I meant by comparing the available info. You could query Marathon's > /v2/apps endpoint to get the list of pending tasks and the resources > requested for each of them, and you could check the Mesos master and slave > /statistics.json to see the total amount of unallocated resources to estimate > how many additional resources you need for how many instances (may need > unique hosts) of pending tasks. Then you would have to map this onto a > request in a (cloud) provisioning tool for X more nodes with Y resources each. > > Alternatively, you could use this same information, along with some notion of > relative priority to kill off (and scale down) lower priority tasks until you > have enough resources to satisfy your higher priority tasks. > >> On Mon, May 4, 2015 at 10:32 AM, Tim Chen <[email protected]> wrote: >> Hi Yaron, >> >> Marathon itself has its own REST endpoint you can hit (/v2/apps) that will >> return to you all the apps and tasks information, so you can see how many of >> the apps are launched and how many are still pending. >> >> Tim >> >>> On Mon, May 4, 2015 at 5:28 AM, Yaron Rosenbaum <[email protected]> >>> wrote: >>> Hi Adam, >>> >>> For example, with Marathon - how can I get the list of pending tasks ? and >>> by “how many additional nodes you would need to satisfy them” - do you >>> mean, by comparing the two? or is there statistics for that too? >>> >>> Thanks >>> >>> (Y) >>> >>>> On May 3, 2015, at 10:10 AM, Adam Bordelon <[email protected]> wrote: >>>> >>>> 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) >
