ASF GitHub Bot commented on IGNITE-5943:

GitHub user EdShangGG opened a pull request:




You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/gridgain/apache-ignite IGNITE-5943

Alternatively you can review and apply these changes as the patch at:


To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #2423
commit 2d93a7c11871a2b23cfb2e6f9854dccb48eac4f1
Author: Andrey Novikov <anovi...@gridgain.com>
Date:   2017-08-03T03:42:08Z

    IGNITE-5888 Web Console: Fixed maven project generation.

commit 36787e149693103fa22ba4093259d2fd8425689a
Author: Andrey Novikov <anovi...@gridgain.com>
Date:   2017-08-03T03:45:59Z

    IGNITE-5906 Fixed race on activities merge.

commit 9e9f1d1e4cdcb3ade018f3eabcf2b2d10a7c003b
Author: tledkov-gridgain <tled...@gridgain.com>
Date:   2017-08-04T08:16:52Z

    IGNITE-5920: Fixed CacheClientBinaryQueryExample": set 
CacheKeyConfiguration explicitly to enable affinity co-location. This closes 

commit 944056e5431b6018bb653c563db1356f0148fb9a
Author: anovikov <anovi...@gridgain.com>
Date:   2017-08-04T11:10:36Z

    IGNITE-5908 Restore splash.

commit a1652b8f7748d3bf1e42437f9ad36f6f44e19bf5
Author: Sergey Chugunov <sergey.chugu...@gmail.com>
Date:   2017-08-07T08:34:01Z

    IGNITE-5950 incorrect assertion fixed

commit cfa5ac269c37718191be42d5554637b78c2a7466
Author: Eduard Shangareev <eshangar...@gridgain.com>
Date:   2017-08-09T15:57:24Z

    IGNITE-5943 Communication. Server node may reject client connection during 
massive clients join


> 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: Eduard Shangareev
>            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

Reply via email to