[
https://issues.apache.org/jira/browse/KNOX-986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16108738#comment-16108738
]
Zsombor Gegesy commented on KNOX-986:
-------------------------------------
I fear, this is not enough to solve the OutOfMemory issue, as the
MetricsRegistry will contain an enourmous amount of instances from
com.codahale.metrics.Timer as the InstrumentationProvider still try to collect
the stats, even when gateway.metrics.enabled is set to false.
If gateway.metrics.enabled is set to false, then this should be disabled as
well.
> JMX Metric Reporter and OutOfMemory Issues
> ------------------------------------------
>
> Key: KNOX-986
> URL: https://issues.apache.org/jira/browse/KNOX-986
> Project: Apache Knox
> Issue Type: Bug
> Components: Server
> Reporter: Larry McCay
> Fix For: 0.13.0
>
> Attachments:
> 0001-KNOX-986-change-the-default-of-the-metric-collection.patch
>
>
> Each unique URL is resulting in a new metric and the JMX reporter is keeping
> it all in memory. This can lead to OOM exceptions and require a server
> restart.
> We need to revisit the metrics and consider whether every single URL needs a
> metric or whether we can configure the level of granularity.
> Unfortunately, metrics collection with the JMX reporter is enabled by default.
> This JIRA should change the default to not be disabled.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
