ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Semen Boikov (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (IGNITE-5578) Discovery events coalescing
Date Wed, 30 Aug 2017 09:18:00 GMT

     [ https://issues.apache.org/jira/browse/IGNITE-5578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Semen Boikov reassigned IGNITE-5578:
------------------------------------

    Assignee:     (was: Semen Boikov)

> Discovery events coalescing
> ---------------------------
>
>                 Key: IGNITE-5578
>                 URL: https://issues.apache.org/jira/browse/IGNITE-5578
>             Project: Ignite
>          Issue Type: Improvement
>          Components: cache, general
>    Affects Versions: 1.0
>            Reporter: Alexey Goncharuk
>             Fix For: 2.3
>
>
> There is an issue that has been in Ignite long ago and with the growing community and
growing cluster sizes, it becomes more tangible.
> When a bunch of nodes leave or join cluster, we generate a separate discovery event for
each node, and each discovery event generates a partition map exchange. 
> The first idea that came to my mind was to coalesce the partition map exchanges, but
this is extremely difficult to implement on unstable topology.
> Instead, we can introduce NODES_JOINED / NODES_FAILED events and batch multiple events
on discovery level when possible. In this case, very few extra partition map exchanges are
possible.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message