You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Nikolay Izhikov (Jira)" <ji...@apache.org> on 2023/01/24 16:33:00 UTC
[jira] [Resolved] (IGNITE-18434) Сustom histogram buckets not applied after restart
[ https://issues.apache.org/jira/browse/IGNITE-18434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nikolay Izhikov resolved IGNITE-18434.
--------------------------------------
Resolution: Not A Bug
Metric configuration stored in DistributedMetastorage.
To enable it, please, enable persistent of default data region
> Сustom histogram buckets not applied after restart
> --------------------------------------------------
>
> Key: IGNITE-18434
> URL: https://issues.apache.org/jira/browse/IGNITE-18434
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 2.14
> Reporter: Stepanov Ilya
> Priority: Minor
> Labels: ise
>
> Setting custom buckets for "TaskExecutionTime" metric in "threadPools.\{thread_pool_name}" register is not applied after node restart.
>
> Steps to reproduce:
> 1) Start node
> 2) change buckets for TaskExecutionTime in StripedExecutor (via configureHistogramMetric [https://javadoc.io/static/org.apache.ignite/ignite-core/2.14.0/org/apache/ignite/mxbean/MetricsMxBean.html#configureHistogramMetric-java.lang.String-long:A-])
> 3) Check metrics in JMX "org.apache:group=threadPools,name=StripedExecutor"
> 4) Restart node
> 5) Check metrics in JMX "org.apache:group=threadPools,name=StripedExecutor"
--
This message was sent by Atlassian Jira
(v8.20.10#820010)