Re: large task scheduling on multi-framework cluster

Note that with the newest marathon that is capable of handling multiple roles, you would not need to run a dedicated marathon instance. On Tue, Oct 1, 2019 at 8:17 AM Grégoire Seux wrote: > Hello, > > I'm wondering how other mesos users deal with scheduling of large tasks > (using all resources

RE: Task list node

Yes thanks managed to get them with this curl -s --user test:xxx --cacert /etc/pki/ca-trust/source/ca-test.crt -X GET https://m01.local:5050/state | jq '.frameworks[].tasks[] | select(.state=="TASK_RUNNING") | del(.statuses, .discovery, .container, .health_check) | "\(.name) \(.state)

large task scheduling on multi-framework cluster

Hello, I'm wondering how other mesos users deal with scheduling of large tasks (using all resources offered by most agents). On our cluster, we have various application launched mainly by marathon. Some of those applications have large instances (30 cpus) which use all resources from agents

Re: Task list node

You can just mimic UI behaviour and use /state endpoint and filter it with jq. wt., 1 paź 2019 o 13:56 Marc Roos napisał(a): > > > Hmmm, if do something like this[0] I get only 3 tasks, and the mesos gui > on 5050 is showing all (I guess, at least more than three) Also if I > grep the

RE: Task list node

Hmmm, if do something like this[0] I get only 3 tasks, and the mesos gui on 5050 is showing all (I guess, at least more than three) Also if I grep the unfiltered json output for a task string, it does not find it. [0] curl -s --user test:xxx --cacert /etc/pki/ca-trust/source/ca-test.crt -X