[
https://issues.apache.org/jira/browse/MESOS-2157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14545938#comment-14545938
]
Adam B edited comment on MESOS-2157 at 5/15/15 6:28 PM:
--------------------------------------------------------
How about a `/master/frameworks/\{framework\}/executors` endpoint too? Just ran
across the fact that master/state.json doesn't seem to report executorInfos
(and their resources).
was (Author: adam-mesos):
How about a /master/frameworks/{framework}/executors endpoint too? Just ran
across the fact that master/state.json doesn't seem to report executorInfos
(and their resources).
> 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)
