[
https://issues.apache.org/jira/browse/MESOS-4740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15190096#comment-15190096
]
Benjamin Mahler commented on MESOS-4740:
----------------------------------------
Hey [~wangcong] [~idownes], did you guys investigate why computing metrics
takes 30 seconds? It's entirely possible that allocator backup / master backup
is where most of the 30 seconds is spent, at which point optimizing the gauge
computation would be useless. Or was it the case that computing all of the
gauge values took 30 seconds? (Seems unlikely).
> 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)
