You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Cong Wang (JIRA)" <ji...@apache.org> on 2016/03/07 23:54:41 UTC

[jira] [Updated] (MESOS-4740) Improve master metrics/snapshot performace

     [ https://issues.apache.org/jira/browse/MESOS-4740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Cong Wang updated MESOS-4740:
-----------------------------
    Summary: Improve master metrics/snapshot performace  (was: Improve metrics/snapshot performace)

> 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 metrics/snapshot could take such a long time to complete under load, since we don't use history for these statistics and the values are just some atomic read.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)