You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Alexey Goncharuk (JIRA)" <ji...@apache.org> on 2017/06/16 11:07:00 UTC
[jira] [Created] (IGNITE-5521) Large near caches lead to cluster
instability with metrics enabled
Alexey Goncharuk created IGNITE-5521:
----------------------------------------
Summary: Large near caches lead to cluster instability with metrics enabled
Key: IGNITE-5521
URL: https://issues.apache.org/jira/browse/IGNITE-5521
Project: Ignite
Issue Type: Bug
Components: cache, general
Affects Versions: 1.7
Reporter: Alexey Goncharuk
Fix For: 2.2
We have two issues in the way cache metrics are working:
1) Near cache size is calculated using full iteration over the near entries. Perhaps, this is done because of near entries may be invalidated by a primary node change, however, we should give a less strict metric rather than O(N) cache size time
2) Cache metrics are copied in discovery worker threads. This looks a bit risky because an error like the one described before may stall the whole cluster. We need to make sure that when the heartbeat message is processed, we already have a metrics snapshot enabled
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)