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

ASF GitHub Bot commented on IGNITE-6826:
----------------------------------------

GitHub user SomeFire opened a pull request:

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

    IGNITE-6826

    

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

    $ git pull https://github.com/SomeFire/ignite ignite-6826

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

    https://github.com/apache/ignite/pull/3362.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 #3362
    
----
commit cd268cf53b769d26e3ae8a243013cb028569a846
Author: Dmitrii Ryabov <somefireone@...>
Date:   2017-12-27T10:25:39Z

    IGNITE-6826: ipFinder changed in java examples.

commit 78783a17fb625b854a7a3e3fa86bea918b2b2637
Author: Dmitrii Ryabov <somefireone@...>
Date:   2018-01-11T14:11:11Z

    IGNITE-6826: ipFinder changed in dotnet examples.

commit 69f85efa93195de88e691368b333f3633504ce50
Author: Dmitrii Ryabov <somefireone@...>
Date:   2018-01-11T14:16:53Z

    IGNITE-6826: ipFinder changed in cpp examples.

----


> Change default DiscoverySpi ipFinder type for examples
> ------------------------------------------------------
>
>                 Key: IGNITE-6826
>                 URL: https://issues.apache.org/jira/browse/IGNITE-6826
>             Project: Ignite
>          Issue Type: Improvement
>          Components: examples
>    Affects Versions: 2.3
>            Reporter: Alexey Popov
>            Assignee: Ryabov Dmitrii
>              Labels: newbie
>
> It is better to change multicast ipFinder to static (vm) ipFinder for java 
> examples, .NET examples and C++ examples.
> http://apache-ignite-developers.2346864.n4.nabble.com/ipFinder-configuration-for-Samples-td23818.html



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

Reply via email to