You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Alexander Rojas (JIRA)" <ji...@apache.org> on 2015/04/20 12:10:59 UTC

[jira] [Commented] (MESOS-2157) Add /master/slaves and /master/frameworks/{framework}/tasks/{task} endpoints

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

Alexander Rojas commented on MESOS-2157:
----------------------------------------

This one will simplify testing:
https://reviews.apache.org/r/32163/

> 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)