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 2015/06/10 08:23:01 UTC

[jira] [Assigned] (IGNITE-1003) Communication issues when running client node in separate subnetwork

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

Semen Boikov reassigned IGNITE-1003:
------------------------------------

    Assignee: Semen Boikov

> Communication issues when running client node in separate subnetwork
> --------------------------------------------------------------------
>
>                 Key: IGNITE-1003
>                 URL: https://issues.apache.org/jira/browse/IGNITE-1003
>             Project: Ignite
>          Issue Type: Bug
>          Components: general
>    Affects Versions: sprint-4
>            Reporter: Valentin Kulichenko
>            Assignee: Semen Boikov
>            Priority: Blocker
>             Fix For: sprint-5
>
>         Attachments: client.zip, server.zip, test.xml
>
>
> Test is the following:
> * Run 8 server nodes on one box.
> * Start and stop client node in a loop on a different box in different subnetwork (e.g., over VPN).
> On one if iterations node join process will hang for several minutes due to timeouts in initial partition exchange. At some point communication between some of the server nodes stops working - messages wait in queue until connection is closed and these messages are recovered.
> Attached are configuration file used to run the test and logs with communication debug enabled.



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