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

["Bernd Mathiske (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MESOS-2157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bernd Mathiske updated MESOS-2157:
----------------------------------
    Sprint: Mesosphere Q1 Sprint 2 - 2/6, Mesosphere Q1 Sprint 3 - 2/20, Mesosphere Q1 Sprint 4 - 3/6, Mesosphere Q1 Sprint 5 - 3/20, Mesosphere Q1 Sprint 6 - 4/3, Mesosphere Q1 Sprint 7 - 4/17, Mesosphere Q2 Sprint 8 - 5/1, Mesosphere Q1 Sprint 9 - 5/15  (was: Mesosphere Q1 Sprint 2 - 2/6, Mesosphere Q1 Sprint 3 - 2/20, Mesosphere Q1 Sprint 4 - 3/6, Mesosphere Q1 Sprint 5 - 3/20, Mesosphere Q1 Sprint 6 - 4/3, Mesosphere Q1 Sprint 7 - 4/17, Mesosphere Q2 Sprint 8 - 5/1)

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