You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@mesos.apache.org by Diogo Gomes <di...@gmail.com> on 2015/12/28 23:09:19 UTC
More filters on /master/tasks enpoint and filters on /master/state
Hi guys, I would like your opinion about a future feature proposal.
Currently, we can use HTTP API to list all our tasks running in our cluster
using /master/tasks, but you have to list all tasks or limit/offset this
list, we cannot filter this. I would like to filter this, using labels, for
example. The use case will be to use mesos to fill our load balancer with
tasks data.
Marathon currently provides something like this, but only for his tasks,
using /v2/apps/?label=[key]==[value]
Diogo Gomes
Re: More filters on /master/tasks enpoint and filters on /master/state
Posted by Adam Bordelon <ad...@mesosphere.io>.
See also:
https://issues.apache.org/jira/browse/MESOS-2258 - Enable filtering of task
information in master/state.json
https://issues.apache.org/jira/browse/MESOS-2353 - Improve performance of
the state.json endpoint for large clusters.
https://issues.apache.org/jira/browse/MESOS-2157 - Add /master/slaves and
/master/frameworks/{framework}/tasks/{task} endpoints
https://docs.google.com/document/d/1dU4e8V6CbomWqHae4FnawZdgK131Iu_YN9uRxZ_y-fw/edit#heading=h.s63wu75ck9qy
- Unraveling of the /state.json endpoint
cc: Alexander, MPark
On Mon, Dec 28, 2015 at 6:20 PM, Klaus Ma <kl...@gmail.com> wrote:
> +1
>
> It'll also reduce master's workload; but instead of label, I'd like to
> make master simpler: return tasks page by page and let framework/dashboard
> to filter it themself.
>
>
> ----
> Da (Klaus), Ma (马达) | PMP® | Advisory Software Engineer
> Platform Symphony/DCOS Development & Support, STG, IBM GCG
> +86-10-8245 4084 | klaus1982.cn@gmail.com | http://k82.me
>
> On Tue, Dec 29, 2015 at 6:09 AM, Diogo Gomes <di...@gmail.com> wrote:
>
>> Hi guys, I would like your opinion about a future feature proposal.
>>
>> Currently, we can use HTTP API to list all our tasks running in our
>> cluster using /master/tasks, but you have to list all tasks or limit/offset
>> this list, we cannot filter this. I would like to filter this, using
>> labels, for example. The use case will be to use mesos to fill our load
>> balancer with tasks data.
>>
>>
>> Marathon currently provides something like this, but only for his tasks,
>> using /v2/apps/?label=[key]==[value]
>>
>>
>> Diogo Gomes
>>
>
>
Re: More filters on /master/tasks enpoint and filters on /master/state
Posted by Klaus Ma <kl...@gmail.com>.
+1
It'll also reduce master's workload; but instead of label, I'd like to make
master simpler: return tasks page by page and let framework/dashboard to
filter it themself.
----
Da (Klaus), Ma (马达) | PMP® | Advisory Software Engineer
Platform Symphony/DCOS Development & Support, STG, IBM GCG
+86-10-8245 4084 | klaus1982.cn@gmail.com | http://k82.me
On Tue, Dec 29, 2015 at 6:09 AM, Diogo Gomes <di...@gmail.com> wrote:
> Hi guys, I would like your opinion about a future feature proposal.
>
> Currently, we can use HTTP API to list all our tasks running in our
> cluster using /master/tasks, but you have to list all tasks or limit/offset
> this list, we cannot filter this. I would like to filter this, using
> labels, for example. The use case will be to use mesos to fill our load
> balancer with tasks data.
>
>
> Marathon currently provides something like this, but only for his tasks,
> using /v2/apps/?label=[key]==[value]
>
>
> Diogo Gomes
>