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 2016/12/27 10:58:58 UTC

[jira] [Commented] (IGNITE-4499) TcpDiscoverySpi is not reliable in some network split scenarios.

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

Alexei Scherbakov commented on IGNITE-4499:
-------------------------------------------

Sadly I have no reproducer at the moment.

> TcpDiscoverySpi is not reliable in some network split scenarios.
> ----------------------------------------------------------------
>
>                 Key: IGNITE-4499
>                 URL: https://issues.apache.org/jira/browse/IGNITE-4499
>             Project: Ignite
>          Issue Type: Bug
>          Components: general
>    Affects Versions: 1.6
>            Reporter: Alexei Scherbakov
>             Fix For: 2.0
>
>
> Where is a possible caveat in current discovery implementation using ring of nodes.
> Imagine grid consisting of nodes A B C D
> Let them form the ring:
> A-B-C-D-A
> If network connectivity issues will arise between nodes A-C and B-D
> discovery spi will never know it and will continue to assume the topology is valid. 
> On other side, TcpCommunicationSpi will try to run transaction on this topology and never will succeed.
> We must drop nodes from topology on communication spi errors.



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