Yakov,

First, it doesn’t seem likely that many people would run examples on several 
machines. Even if someone would, they’d probably start doing so after some 
experimentation with a single host – at the moment when they’re already 
adjusted enough to check and edit some configs.

Second, I don’t think that this use case outweighs the troubles new (and even 
experienced) users get because of the multicast.
Even if it helps some users to get started in their first 30 minutes with 
Ignite, it will just as well confuse them later and leave a feeling of unstable 
product.

Showing a warning with default settings is confusing – a user didn’t do 
anything wrong, and still we smack their hand with a warning.
I believe we should use warnings for erroneous conditions only.

Thanks,
Stan

From: Yakov Zhdanov
Sent: 19 июля 2018 г. 16:54
To: dev@ignite.apache.org
Cc: antkr....@gmail.com; somefire...@gmail.com; ptupit...@apache.org
Subject: Re: Pushing IGNITE-6826 forward

Guys, multicast IP finder gives new user an opportunity to run tests on
several machines with zero config changes. And you want to change this
which is not good in my view.

Probably, we need to output warning pointing that user can change multicast
group to avoid undesired discovery and isolate several clusters in the same
network.

--Yakov

2018-07-18 17:30 GMT+03:00 Dmitry Pavlov <dpavlov....@gmail.com>:

> Hi Stanislav,
>
> I wish this push will have effect.
>
> Just two proposals that will help Igniters to easily jump into such emails:
> 1. Include ticket short description into subject, not only number.
> 2. Include link to JIRA issue into body so it could be easily clicked to
> find out details.
> It can seem not important, but saves a minute for everyone.
>
> Sincerely,
> Dmitriy Pavlov
>
> ср, 18 июл. 2018 г. в 16:32, Stanislav Lukyanov <stanlukya...@gmail.com>:
>
> > Hi Igniters,
> >
> > There is a small but annoying issue with examples using MulticastIpFinder
> > by default.
> > The JIRA is  IGNITE-6826.
> >
> > AntonK and DmitriiR have suggested PRs to fix this, but PavelT had some
> > concerns and the fix stuck as the result.
> >
> > Pavel, could you please suggest necessary changes to the PRs so that guys
> > can move forward with integration?
> >
> > Thanks,
> > Stan
> >
>

Reply via email to