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 2016/09/27 12:44:20 UTC

[jira] [Resolved] (IGNITE-3973) Nodes can form separate clusters with TcpDiscoveryMulticastIpFinder

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

Semen Boikov resolved IGNITE-3973.
----------------------------------
    Resolution: Fixed
      Assignee:     (was: Semen Boikov)

Changed TcpDiscoveryMulticastIpFinder.requestAddresses to do not stop when first remote address is received.

Better fix is send together with adress flag indicating whether node already joined topology, requestAddresses can stop when address from joined node is received. But this breaks binary compatibility.

> Nodes can form separate clusters with TcpDiscoveryMulticastIpFinder
> -------------------------------------------------------------------
>
>                 Key: IGNITE-3973
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3973
>             Project: Ignite
>          Issue Type: Bug
>          Components: general
>    Affects Versions: 1.7
>            Reporter: Semen Boikov
>            Priority: Critical
>             Fix For: 1.8
>
>
> Currently TcpDiscoveryMulticastIpFinder on start sends mcast address request and stops wait when at least one remote address is received.
> This scenario is possible:
> - 4 nodes start concurrently
> - node1 receive first address of node2, node2 from node1
> - node3 receive first address of node4, node4 from node3
> - node1/node2 and node3/node4 can form separate clusters



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)