[
https://issues.apache.org/jira/browse/MESOS-4740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15199863#comment-15199863
]
Michael Park commented on MESOS-4740:
-------------------------------------
{noformat}
commit 8be869abab468706274e435247e8e22eef0dd0a0
Author: Cong Wang <[email protected]>
Date: Thu Mar 17 12:14:00 2016 -0400
Updated `/metrics/snapshot` endpoint to use `jsonify`.
Review: https://reviews.apache.org/r/44675/
{noformat}
NOTE: committed more so under: https://issues.apache.org/jira/browse/MESOS-4732
> Improve master metrics/snapshot performace
> ------------------------------------------
>
> Key: MESOS-4740
> URL: https://issues.apache.org/jira/browse/MESOS-4740
> Project: Mesos
> Issue Type: Task
> Reporter: Cong Wang
> Assignee: Cong Wang
>
> [~drobinson] noticed retrieving metrics/snapshot statistics could be very
> inefficient.
> {noformat}
> [user@server ~]$ time curl -s localhost:5050/metrics/snapshot
> real 0m35.654s
> user 0m0.019s
> sys 0m0.011s
> {noformat}
> MESOS-1287 introduces a timeout parameter for this query, but for
> metric-collectors like ours they are not aware of such URL-specific
> parameter, so we need:
> 1) We should always have a timeout and set some default value to it
> 2) Investigate why master metrics/snapshot could take such a long time to
> complete under load.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
