You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Eduard Shangareev (JIRA)" <ji...@apache.org> on 2017/08/10 14:09:02 UTC

[jira] [Comment Edited] (IGNITE-5943) Communication. Server node may reject client connection during massive clients join

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

Eduard Shangareev edited comment on IGNITE-5943 at 8/10/17 2:08 PM:
--------------------------------------------------------------------

PR - https://github.com/apache/ignite/pull/2423
Test Run - https://ci.ignite.apache.org/viewQueued.html?itemId=764991&tab=queuedBuildOverviewTab


was (Author: edshanggg):
PR - https://github.com/apache/ignite/pull/2423
Test Run - https://ci.ignite.apache.org/viewQueued.html?itemId=764905&tab=queuedBuildOverviewTab

> Communication. Server node may reject client connection during massive clients join
> -----------------------------------------------------------------------------------
>
>                 Key: IGNITE-5943
>                 URL: https://issues.apache.org/jira/browse/IGNITE-5943
>             Project: Ignite
>          Issue Type: Bug
>          Components: general
>    Affects Versions: 2.0
>            Reporter: Eduard Shangareev
>            Assignee: Yakov Zhdanov
>            Priority: Critical
>             Fix For: 2.2
>
>
> There is a race between a client join discovery event on server nodes and the moment when a client starts to establish outgoing communication connections. It would cause to rejecting communication connections on server nodes (for example. on requesting data from caches).
> The issue happens on really big topologies (> 300 nodes) or when many clients join simultaneously.



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