You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by Alexey Popov <ta...@gmail.com> on 2017/11/03 08:14:14 UTC
Re: ipFinder configuration for Samples
I've created https://issues.apache.org/jira/browse/IGNITE-6826
Thanks,
Alexey
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Re: ipFinder configuration for Samples
Posted by Dmitrii Ryabov <so...@gmail.com>.
Yakov,
I checked hazelcast - it uses multicast by default.
чт, 28 февр. 2019 г., 14:31 Stanislav Lukyanov <st...@gmail.com>:
> Yakov,
>
> Our product is for engineers sitting in one office.
> Companies which use Ignite have many engineers running Ignite on their
> laptops the same way
> as companies that make changes to Ignite.
> “Could it be because of the multicast?” is one of the questions I ask
> every time I see a question on SO
> or user list, and I would be happy not to.
>
> The activity of changing the examples from multicast to local addresses
> was started and stopped multiple times,
> but AFAIR most of the community was in favor of this change.
>
> Moreover, our default configuration (when discoSpi is not set– such as in
> default-config.xml)
> uses multicast. I’d change that to a localhost VmIPFinder.
>
> If we want an easy start of the examples (even though I think each user
> would want to use examples with multicast
> exactly once, if ever) let’s add multiple configs or a switch to
> ignite.sh. I believe it’s better than showing multicast as default.
>
> Regarding the address list – AFAIR Ignite tries to scan the multicast
> group first. Only after that it
> will try to connect to addresses from the list. So, the list is a bit
> misleading.
>
> Finally, if Hazelcast uses multicast by default – well, probably they
> should turn that off as well.
>
> My 2 cents,
> Stan
>
> From: Yakov Zhdanov
> Sent: 28 февраля 2019 г. 12:53
> To: dev@ignite.apache.org
> Subject: Re: ipFinder configuration for Samples
>
> 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
>
>
Re: ipFinder configuration for Samples
Posted by Yakov Zhdanov <yz...@apache.org>.
Stan, I thnk we never know the truth here. Imagine you never dealed with
distributed systems. You just copy distibs to intended machines and startup
distributed cluster out of the box. Is not it good? If we do the change we
should expect many questions to user@ asking why nodes do not see each
other. Agree?
--Yakov
RE: ipFinder configuration for Samples
Posted by Stanislav Lukyanov <st...@gmail.com>.
Yakov,
Our product is for engineers sitting in one office.
Companies which use Ignite have many engineers running Ignite on their laptops the same way
as companies that make changes to Ignite.
“Could it be because of the multicast?” is one of the questions I ask every time I see a question on SO
or user list, and I would be happy not to.
The activity of changing the examples from multicast to local addresses was started and stopped multiple times,
but AFAIR most of the community was in favor of this change.
Moreover, our default configuration (when discoSpi is not set– such as in default-config.xml)
uses multicast. I’d change that to a localhost VmIPFinder.
If we want an easy start of the examples (even though I think each user would want to use examples with multicast
exactly once, if ever) let’s add multiple configs or a switch to ignite.sh. I believe it’s better than showing multicast as default.
Regarding the address list – AFAIR Ignite tries to scan the multicast group first. Only after that it
will try to connect to addresses from the list. So, the list is a bit misleading.
Finally, if Hazelcast uses multicast by default – well, probably they should turn that off as well.
My 2 cents,
Stan
From: Yakov Zhdanov
Sent: 28 февраля 2019 г. 12:53
To: dev@ignite.apache.org
Subject: Re: ipFinder configuration for Samples
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
Re: ipFinder configuration for Samples
Posted by Yakov Zhdanov <yz...@apache.org>.
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
Re: ipFinder configuration for Samples
Posted by Yakov Zhdanov <yz...@apache.org>.
Guys, I remember we did this to
--Yakov
ср, 27 февр. 2019 г. в 14:46, Dmitrii Ryabov <so...@gmail.com>:
> Hello, Igniters!
>
> Code is ready and reviewed, tests are passed.
>
> Can we make final decision about this change? Do we really need it? [1]
>
> Pros:
>
> * 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.
> * Same change was made for test framework [2].
>
> [1]
>
> https://issues.apache.org/jira/browse/IGNITE-6826?focusedCommentId=16752473&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16752473
> [2] https://issues.apache.org/jira/browse/IGNITE-10555
>
> пт, 3 нояб. 2017 г., 11:14 Alexey Popov <ta...@gmail.com>:
>
> > I've created https://issues.apache.org/jira/browse/IGNITE-6826
> >
> > Thanks,
> > Alexey
> >
> >
> >
> > --
> > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
> >
>
Re: ipFinder configuration for Samples
Posted by Dmitrii Ryabov <so...@gmail.com>.
Hello, Igniters!
Code is ready and reviewed, tests are passed.
Can we make final decision about this change? Do we really need it? [1]
Pros:
* 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.
* Same change was made for test framework [2].
[1]
https://issues.apache.org/jira/browse/IGNITE-6826?focusedCommentId=16752473&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16752473
[2] https://issues.apache.org/jira/browse/IGNITE-10555
пт, 3 нояб. 2017 г., 11:14 Alexey Popov <ta...@gmail.com>:
> I've created https://issues.apache.org/jira/browse/IGNITE-6826
>
> Thanks,
> Alexey
>
>
>
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>