[
https://issues.apache.org/jira/browse/IGNITE-6826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16739399#comment-16739399
]
Anton Vinogradov commented on IGNITE-6826:
------------------------------------------
Folks,
First of all, let's define why \{{it is better to change multicast ipFinder to
static (vm) ipFinder}}.
Second, and most important, once you'll change multicast to vm you not be able
to check how examples work with
- nodes, started by ignite.bat/sh
- nodes, started by ExampleNodeStartup
In short, it's not allowed to change multicast to vm where you have to or may
want to start nodes at different JVM.
Also, please keep im mind that we have to check how fix works inside assembled
Apache Ignite before changing status to PA.
> 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
> Priority: Major
> Labels: newbie
> Fix For: 2.8
>
>
> 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
(v7.6.3#76005)
