You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Aleksey Plekhanov (Jira)" <ji...@apache.org> on 2020/07/03 06:41:00 UTC
[jira] [Updated] (IGNITE-10912) Huge discovery messages slow down
node joining/dynamic cache start and corresponding PME
[ https://issues.apache.org/jira/browse/IGNITE-10912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aleksey Plekhanov updated IGNITE-10912:
---------------------------------------
Fix Version/s: (was: 2.9)
> Huge discovery messages slow down node joining/dynamic cache start and corresponding PME
> ----------------------------------------------------------------------------------------
>
> Key: IGNITE-10912
> URL: https://issues.apache.org/jira/browse/IGNITE-10912
> Project: Ignite
> Issue Type: Improvement
> Reporter: Alexey Scherbakov
> Priority: Major
>
> WIth large topology and large number of caches/groups node join message can reach a size > 30M due to a large amount of transferred discovery data.
> It adds overhead on ring traversal and slows down "node join" PME.
> Possible solution:
> # introduce DiscoveryDataMessage for transferring discovery related data which doesn't increment topology version. After all nodes wil have corressponding discovery data start actual joining. Discovery data probably should be stored off-heap(or even on disk) to avoid heap usage bursts on joining of multiple nodes.
> # Add compression to discovery data.
> Same problem for CacheAffinityChangeMessage (PME after late affinity) and dynamic cache start message (if starting many caches).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)