You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Semen Boikov (JIRA)" <ji...@apache.org> on 2017/08/21 15:49:00 UTC

[jira] [Resolved] (IGNITE-6124) Try merge multiple exchanges into one

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

Semen Boikov resolved IGNITE-6124.
----------------------------------
    Resolution: Fixed

Implemented initial version (commit bebf299799712b464ee0e3800752ecc07770d9f0). For now exchanges for custom events (e.g. cache start) are not merged, but technically it is also possible.

> Try merge multiple exchanges into one
> -------------------------------------
>
>                 Key: IGNITE-6124
>                 URL: https://issues.apache.org/jira/browse/IGNITE-6124
>             Project: Ignite
>          Issue Type: Improvement
>          Components: cache
>            Reporter: Semen Boikov
>            Assignee: Semen Boikov
>            Priority: Critical
>             Fix For: 2.2
>
>
> Currently if multiple nodes simultaneously join or fail, on each discovery event separate partition exchange process is started. It is possible to optimize this and process multiple discovery events in single partition exchange.



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