[
https://issues.apache.org/jira/browse/MESOS-2157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14577896#comment-14577896
]
Marco Massenzio commented on MESOS-2157:
----------------------------------------
[~arojas] Can you please update this story?
Is this still going to be committed, or should it moved back from
{{Reviewable}}?
Also, I'm estimating it at 5 points (the time the review just sat there, should
not count towards this) but please let me know if it was much more effort to
implement.
Keeping in the Backlog for now.
> 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)
