[
https://issues.apache.org/jira/browse/IGNITE-12844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17070004#comment-17070004
]
Ignite TC Bot commented on IGNITE-12844:
----------------------------------------
{panel:title=Branch: [pull/7582/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5165301&buildTypeId=IgniteTests24Java8_RunAll]
> Too many caches can block discovery
> -----------------------------------
>
> Key: IGNITE-12844
> URL: https://issues.apache.org/jira/browse/IGNITE-12844
> Project: Ignite
> Issue Type: Bug
> Reporter: Philipp Masharov
> Assignee: Philipp Masharov
> Priority: Major
> Fix For: 2.9
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Several thousand caches send metrics in each discovery message.
> Check implementation of `TcpDiscoveryMetricsUpdateMessage`
> This behavior increases processing time and raises message size. As a result,
> the discovery worker is busy and the queue pool is growing.
> We need to notify about the possible issue and print suggestion, for example,
> `-DIGNITE_DISCOVERY_DISABLE_CACHE=true` if it can help. Assumes to print WARN
> message once, for example, if TcpDiscoveryMetricsUpdateMessage consists of
> more than 500 CacheMetricsSnaphot instances.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
