[ https://issues.apache.org/jira/browse/AMBARI-18331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15474488#comment-15474488 ]
Hudson commented on AMBARI-18331: --------------------------------- FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5638 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5638/]) AMBARI-18331 - JMX metric retrieval method may unnecessarily refresh (jhurley: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=8efbde8fd13be4278017345a4077bebb6f4f366e]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/metrics/RestMetricsPropertyProviderTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/jmx/JMXPropertyProvider.java * (edit) ambari-server/docs/configuration/index.md * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/metrics/RestMetricsPropertyProvider.java * (add) ambari-server/src/test/java/org/apache/ambari/server/state/services/MetricsRetrievalServiceTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/metrics/JMXPropertyProviderTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/services/MetricsRetrievalService.java > 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)