You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by kdudkov <gi...@git.apache.org> on 2016/11/30 10:24:34 UTC

[GitHub] ignite pull request #1300: Ignite 4223

GitHub user kdudkov opened a pull request:

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

    Ignite 4223

    

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

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

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

    https://github.com/apache/ignite/pull/1300.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 #1300
    
----
commit bfb00b6e61f9709718c30971997aeb0ac79e86b4
Author: Alexandr Kuramshin <ak...@gridgain.com>
Date:   2016-11-18T20:12:28Z

    IgniteTcpCommunicationBigClusterTest added

commit 02dd92e605b9b53f5a16c7ec5f8e7b5698b15ba4
Author: Alexandr Kuramshin <ak...@gridgain.com>
Date:   2016-11-18T21:55:37Z

    IgniteTcpCommunicationBigClusterTest update

commit 6acf193a3d356d1bad4c02a53ac76833ed1008d0
Author: Alexandr Kuramshin <ak...@gridgain.com>
Date:   2016-11-19T09:55:45Z

    Have got TcpCommunicationSpi error

commit 4fd39653d24f62f19f70b4dffba8497185cc46fb
Author: Alexandr Kuramshin <ak...@gridgain.com>
Date:   2016-11-19T16:39:10Z

    Some discovery have been done

commit c2c181922c7c24ea457577e32d2af897c8bec87f
Author: Alexandr Kuramshin <ak...@gridgain.com>
Date:   2016-11-19T20:11:28Z

    Prove that problem is not in the onFirstMessage hang

commit f8076edba097f6077229b2090ee3ff1a3369878c
Author: Alexandr Kuramshin <ak...@gridgain.com>
Date:   2016-11-19T20:26:37Z

    Revert: Prove that problem is not in the onFirstMessage hang

commit 6e1f2dfc2acb3dbb8f24aa51ed67b2ee447b4585
Author: Alexandr Kuramshin <ak...@gridgain.com>
Date:   2016-11-21T08:55:09Z

    Revert: pushing unnecessary changes to the master

commit ed794ca815f6bb1471af15779279d287576b39cc
Author: Alexandr Kuramshin <ak...@gridgain.com>
Date:   2016-11-21T09:08:00Z

    Revert: pushing unnecessary changes to the master

commit 3fb723d9e693141830fc3bcff96408f0558fa695
Author: Konstantin Dudkov <kd...@ya.ru>
Date:   2016-11-24T09:49:34Z

    IGNITE-4223

commit a3310154203d92b0ad953636406ca6fae38b7573
Author: Konstantin Dudkov <kd...@ya.ru>
Date:   2016-11-25T09:05:47Z

    IGNITE-4223 wip

commit b8ae8937c8ad0ea0e5037c4a5c339c22a63aaf08
Author: Konstantin Dudkov <kd...@ya.ru>
Date:   2016-11-28T16:28:19Z

    IGNITE-4223

commit ef7f115050189952e6086492d21cba29679ed676
Author: Konstantin Dudkov <kd...@ya.ru>
Date:   2016-11-29T10:21:45Z

    IGNITE-4223

commit c3af4d93592d5b7bf2f32ade65cb30cad68bbdf2
Author: Konstantin Dudkov <kd...@ya.ru>
Date:   2016-11-29T13:39:36Z

    Merge remote-tracking branch 'apache/master' into ignite-4223
    
    # Conflicts:
    #	modules/core/src/main/java/org/apache/ignite/internal/managers/communication/GridIoMessageFactory.java
    #	modules/core/src/main/java/org/apache/ignite/internal/processors/cache/CacheAffinitySharedManager.java

commit 5c01b040b2a9e6fc7d65577f947d565984401ffb
Author: Konstantin Dudkov <kd...@ya.ru>
Date:   2016-11-29T13:56:41Z

    IGNITE-4223 merge fix

commit 6dc69b07a99b45eeadc9e234fe3258724f5a6534
Author: Konstantin Dudkov <kd...@ya.ru>
Date:   2016-11-29T14:21:28Z

    IGNITE-4223

----


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request #1300: Ignite 4223

Posted by kdudkov <gi...@git.apache.org>.
Github user kdudkov closed the pull request at:

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


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---