Guys, I remember we did the opposite change some time ago - switched VM IP finder to multicast. That was done for user being able to start cluster spanning multiple machines using examples configuration. With this change you removed all the working samples for starting really distributed environment.
What was the problem? Multicast IP finder has the list of addresses that we try to connect to on start. As far as clashes - it seems it affects only engineers sitting in one office, but they can set up env var to override default mcast group. The primary goal for switching to multicast was to allow people new to Ignite to quickly start the cluster. As far as I remember hazelcast has multicast enabled by default. Can anybody check this? --Yakov
