Aleksey Plekhanov created IGNITE-10172:
------------------------------------------
Summary: Enabling cache statistics on a large cluster with a large
number of caches can affect performance
Key: IGNITE-10172
URL: https://issues.apache.org/jira/browse/IGNITE-10172
Project: Ignite
Issue Type: Improvement
Affects Versions: 2.6
Reporter: Aleksey Plekhanov
Assignee: Aleksey Plekhanov
Fix For: 2.8
In current implementation cache metrics are collected on each node and sent
across whole cluster with discovery message
({{TcpDiscoveryMetricsUpdateMessage}}) with configured frequency
({{MetricsUpdateFrequency}}, 2 seconds by default).
If there are a lot of caches and a lot of nodes in the cluster, metrics update
message (which contain metrics for each cache on each node) can reach a
critical size.
Also frequently collecting all cache metrics have a negative performance impact.
The only way now to disable cache metrics collecting and sending with discovery
metrics update message is to disable statistics for each cache. But this also
makes impossible to request some of cache metrics locally (for the current node
only). Requesting a limited set of cache metrics on the current node doesn't
have such performance impact as the frequent collecting of all cache metrics,
but sometimes it's enough for diagnostic purposes.
To solve this introduce new system property which will disable cache metrics
sending with {{TcpDiscoveryMetricsUpdateMessage}} even if {{statisticsEnabled}}
flag is true.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
