ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ignite TC Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-10172) Enabling cache statistics on a large cluster with a large number of caches can affect performance
Date Thu, 22 Nov 2018 17:44:00 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-10172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16696158#comment-16696158

Ignite TC Bot commented on IGNITE-10172:

{panel:title=Possible Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Inspections: Core{color} [[tests 0 BuildFailureOnMetric |https://ci.ignite.apache.org/viewLog.html?buildId=2380356]]

[TeamCity Run All Results|https://ci.ignite.apache.org/viewLog.html?buildId=2334055&amp;buildTypeId=IgniteTests24Java8_RunAll]

> Enabling cache statistics on a large cluster with a large number of caches can affect
> -------------------------------------------------------------------------------------------------
>                 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
>            Priority: Major
>             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

View raw message