[
https://issues.apache.org/jira/browse/IGNITE-6826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16741976#comment-16741976
]
Ryabov Dmitrii commented on IGNITE-6826:
----------------------------------------
[~avinogradov],
1. Reasons were discussed on devlist
([1|http://apache-ignite-developers.2346864.n4.nabble.com/ipFinder-configuration-for-Samples-td23818.html],
[2|http://apache-ignite-developers.2346864.n4.nabble.com/Re-Pushing-IGNITE-6826-forward-td32777.html],
[3|http://apache-ignite-developers.2346864.n4.nabble.com/Re-Pushing-forward-IGNITE-6826-Change-default-DiscoverySpi-ipFinder-type-for-examples-td32756.html]).
Summary:
* Multicast ipFinder adds some instability when several persons try & debug
samples or evaluate a new Ignite version at the same local network.
* Speedup for node start.
2. ExampleNodeStartup use the same configuration as examples, so it works as
usual.
See the master branch: {{ExampleNodeStartup}} and {{ignite.bat/sh}} are
*incompatible* because ignite.bat/sh uses default IgniteConfiguration with
disabled peer class loading, but ExampleNodeStartup uses configuration with
enabled peer class loading.
3. I assemled release version asa described in DEVNOTES.txt and checked some
examples manually. They work normally with nodes started by ExampleNodeStartup.
> 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)
