You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Alexei Scherbakov (JIRA)" <ji...@apache.org> on 2017/06/13 16:15:02 UTC

[jira] [Commented] (IGNITE-5385) Get rid of discovery custom message on exchange completion

    [ https://issues.apache.org/jira/browse/IGNITE-5385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16048074#comment-16048074 ] 

Alexei Scherbakov commented on IGNITE-5385:
-------------------------------------------

I've implemented basic handling for exchange completion over CommunicationSpi, introducing new GridDhtFinishExchangeMessage for the purpose.

Now working on corner case when coordinator had left before sending all messages to other nodes.

> Get rid of discovery custom message on exchange completion
> ----------------------------------------------------------
>
>                 Key: IGNITE-5385
>                 URL: https://issues.apache.org/jira/browse/IGNITE-5385
>             Project: Ignite
>          Issue Type: Improvement
>          Components: cache
>    Affects Versions: 2.0
>            Reporter: Yakov Zhdanov
>            Assignee: Alexei Scherbakov
>            Priority: Blocker
>              Labels: performance
>             Fix For: 2.1
>
>
> Currently if late affinity assignment is on we send full partition map as a custom message to make sure all nodes get it. With greater number of nodes and caches this can cause significant slowdowns.
> We suggest to move sending to communication. In this case scenario with coordinator failure requires special handling, since in this case some nodes may receive full map, complete exchange and proceed with cache operations, while others may not received full map yet. In this case full map should be resend from new coordinator - it should be recalculated if none has received one from former coordinator or should be requested from one of the lucky receivers to get forwarded to other nodes.



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