+1 to this. Should we go even further and change Ignite configuration defaults to vm ip finder? Starting a standalone node with default config never works for me, multicast stuff hangs on my network for some reason.
Pavel On Tue, Oct 31, 2017 at 12:00 PM, Evgeniy Ignatiev < yevgeniy.ignat...@gmail.com> wrote: > Also, maybe include in the examples reference to the recommended > failureDetectionTimeout setting and a preset value of 200ms for the local > Ignite (current default is 10 seconds)? It should greatly improve start-up > time for the VM IP finder. > > > > On 10/31/2017 12:37 PM, Sergey Kozlov wrote: > >> +1 >> >> There's the significant slowdown for a node start under Windows if the >> multicast discovery used. >> >> On Tue, Oct 31, 2017 at 10:37 AM, Vladimir Ozerov <voze...@gridgain.com> >> wrote: >> >> Huge +1. We should have VM IP finder with localhost (127.0.0.1). First, >>> there will be no network clashes, second user will see almost correct IP >>> config right away. All he need to change for production usage is IP >>> address. >>> >>> On Tue, Oct 31, 2017 at 9:58 AM, Alexey Popov <tank2.a...@gmail.com> >>> wrote: >>> >>> Hi, Igniters >>>> >>>> I wonder why Ignite examples have multicast ipFinder for DiscoverySpi at >>>> their configuration? >>>> It is a quite common case to try them locally and Vm ipFinder is the >>>> best >>>> option for that. >>>> Multicast ipFinder adds some instability when several persons try & >>>> debug >>>> samples or evaluate a new Ignite version at the same local network. >>>> >>>> It looks like default ipFinder could simplify cluster deployment with >>>> default configs. However, I hardly believe that someone deploys the >>>> >>> samples >>> >>>> into remote hosts without changing IPs. >>>> >>>> I propose to change default configs for examples from multicast to vm >>>> ipFinder. >>>> >>>> Thank you, >>>> Alexey >>>> >>>> >>>> >>>> >>>> -- >>>> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/ >>>> >>>> >> >> >
