[
https://issues.apache.org/jira/browse/MESOS-2258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15962137#comment-15962137
]
Keith Chambers commented on MESOS-2258:
---------------------------------------
In the past week I received 2 reports of clusters where state.json became >
50Mb leading to sluggish to unusable Mesos UI. Workaround is to trigger master
failover, which does work, but is not something the operators of these
particular systems wanted to do on a regular basis.
Support for filtering state.json and implementing filtering in Mesos UI should
resolve this issue.
> Enable filtering of task information in master/state.json
> ---------------------------------------------------------
>
> Key: MESOS-2258
> URL: https://issues.apache.org/jira/browse/MESOS-2258
> Project: Mesos
> Issue Type: Improvement
> Reporter: Niklas Quarfot Nielsen
>
> The masters state endpoint can grow huge (several MB's) in large
> installations due to data of all running and completed tasks, while other
> pieces of information (counters, attached slaves and frameworks) are still
> useful to be polled frequently.
> We can add query parameters to state.json to filter out task information
> and/or introduce a /metadata.json endpoint with all but task information.
> Any thoughts?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
