mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Rojas (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (MESOS-2157) Add /master/slaves and /master/frameworks/{framework}/tasks/{task} endpoints
Date Fri, 08 May 2015 21:59:59 GMT

    [ https://issues.apache.org/jira/browse/MESOS-2157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14280217#comment-14280217
] 

Alexander Rojas edited comment on MESOS-2157 at 5/8/15 9:59 PM:
----------------------------------------------------------------

https://reviews.apache.org/r/29883/ (Commited, see [here|https://issues.apache.org/jira/browse/MESOS-2157?focusedCommentId=14314401&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14314401])


was (Author: arojas):
https://reviews.apache.org/r/29883/

> Add /master/slaves and /master/frameworks/{framework}/tasks/{task} endpoints
> ----------------------------------------------------------------------------
>
>                 Key: MESOS-2157
>                 URL: https://issues.apache.org/jira/browse/MESOS-2157
>             Project: Mesos
>          Issue Type: Task
>          Components: master
>            Reporter: Niklas Quarfot Nielsen
>            Assignee: Alexander Rojas
>            Priority: Trivial
>              Labels: mesosphere, newbie
>
> master/state.json exports the entire state of the cluster and can, for large clusters,
become massive (tens of megabytes of JSON).
> Often, a client only need information about subsets of the entire state, for example
all connected slaves, or information (registration info, tasks, etc) belonging to a particular
framework.
> We can partition state.json into many smaller endpoints, but for starters, being able
to get slave information and tasks information per framework would be useful.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message