GitHub user akuramshingg opened a pull request:

    https://github.com/apache/ignite/pull/1259

    ignite-4111

    

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

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

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

    https://github.com/apache/ignite/pull/1259.patch

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

    This closes #1259
    
----
commit bfb00b6e61f9709718c30971997aeb0ac79e86b4
Author: Alexandr Kuramshin <[email protected]>
Date:   2016-11-18T20:12:28Z

    IgniteTcpCommunicationBigClusterTest added

commit 02dd92e605b9b53f5a16c7ec5f8e7b5698b15ba4
Author: Alexandr Kuramshin <[email protected]>
Date:   2016-11-18T21:55:37Z

    IgniteTcpCommunicationBigClusterTest update

commit 6acf193a3d356d1bad4c02a53ac76833ed1008d0
Author: Alexandr Kuramshin <[email protected]>
Date:   2016-11-19T09:55:45Z

    Have got TcpCommunicationSpi error

commit 4fd39653d24f62f19f70b4dffba8497185cc46fb
Author: Alexandr Kuramshin <[email protected]>
Date:   2016-11-19T16:39:10Z

    Some discovery have been done

commit c2c181922c7c24ea457577e32d2af897c8bec87f
Author: Alexandr Kuramshin <[email protected]>
Date:   2016-11-19T20:11:28Z

    Prove that problem is not in the onFirstMessage hang

commit f8076edba097f6077229b2090ee3ff1a3369878c
Author: Alexandr Kuramshin <[email protected]>
Date:   2016-11-19T20:26:37Z

    Revert: Prove that problem is not in the onFirstMessage hang

commit 9415f11564480ae61952b7ad551518141b5ad7c0
Author: Alexandr Kuramshin <[email protected]>
Date:   2016-11-19T20:55:15Z

    Prove that problem is not in the onFirstMessage hang

commit dc95254a8030f03e485fe535bb286eb1a7b99f63
Author: Alexandr Kuramshin <[email protected]>
Date:   2016-11-21T08:51:26Z

    Hang dectection

commit bcd049d09dadb20295eb87667d20101d7fb41790
Author: Alexandr Kuramshin <[email protected]>
Date:   2016-11-21T19:45:10Z

    Fix: get handshake error on long delivery addNodeFinished message

commit a33f22a9da972b769bf63de04f86b42741c7f0d6
Author: Alexandr Kuramshin <[email protected]>
Date:   2016-11-22T10:39:04Z

    Include the test into Communication SPI Test Suite

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to