ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Hurley (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-18331) JMX metric retrieval method may unnecessarily refresh metrics at a high rate
Date Wed, 07 Sep 2016 13:05:22 GMT

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

Jonathan Hurley updated AMBARI-18331:
-------------------------------------
    Attachment: AMBARI-18331.patch

> JMX metric retrieval method may unnecessarily refresh metrics at a high rate
> ----------------------------------------------------------------------------
>
>                 Key: AMBARI-18331
>                 URL: https://issues.apache.org/jira/browse/AMBARI-18331
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-server
>    Affects Versions: 2.4.0
>            Reporter: Jonathan Hurley
>            Assignee: Jonathan Hurley
>             Fix For: trunk
>
>         Attachments: AMBARI-18331.patch
>
>
> In AMBARI-16913 we revised the JMX retrieval method to maintain an internal state of
JMX metrics, with the retrieval taking place out of band of the actual jetty query requiring
the metric.  However, each query will still generate a refresh request to the metric, regardless
of it's current state.
> Recommend setting a TTL on a given metric such as 5 seconds, and only generate a new
request for the metric if a TTL has expired, to avoid large amounts of repeat metrics collections
in short windows.



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

Mime
View raw message