IGNITE-1401 Introduce special local node discovery events

[voipp]

Hello Igntrs!
I would like to start working on
https://issues.apache.org/jira/browse/IGNITE-1401 if you don't mind.
--

*Best Regards,*

*Kuznetsov Aleksey*

[Vladimir Ozerov]

Hi Aleksey,

I doubt we need this feature at the moment. Local node join is of no use,
since Ignition.start() is synchronous operation, and once control is
returned to the user, he may consider node joined. If node is dropped from
topology, it will never come back, this is already handled by segmentation
mechanics and EVT_NODE_SEGMENTED event. And for client nodes, which could
disconnect and then reconnect, we already have EVT_CLIENT_NODE_DISCONNECTED
and EVT_CLIENT_NODE_RECONNECTED events.

I'll close the ticket as "Won't Fix".

On Fri, May 5, 2017 at 2:44 PM, ALEKSEY KUZNETSOV <[hidden email]>
wrote:

> Hello Igntrs!
> I would like to start working on
> https://issues.apache.org/jira/browse/IGNITE-1401 if you don't mind.
> --
>
> *Best Regards,*
>
> *Kuznetsov Aleksey*
>

[voipp]

great

пт, 5 мая 2017 г. в 14:51, Vladimir Ozerov <[hidden email]>:

> Hi Aleksey,
>
> I doubt we need this feature at the moment. Local node join is of no use,
> since Ignition.start() is synchronous operation, and once control is
> returned to the user, he may consider node joined. If node is dropped from
> topology, it will never come back, this is already handled by segmentation
> mechanics and EVT_NODE_SEGMENTED event. And for client nodes, which could
> disconnect and then reconnect, we already have EVT_CLIENT_NODE_DISCONNECTED
> and EVT_CLIENT_NODE_RECONNECTED events.
>
> I'll close the ticket as "Won't Fix".
>
> On Fri, May 5, 2017 at 2:44 PM, ALEKSEY KUZNETSOV <
> [hidden email]>
> wrote:
>
> > Hello Igntrs!
> > I would like to start working on
> > https://issues.apache.org/jira/browse/IGNITE-1401 if you don't mind.
> > --
> >
> > *Best Regards,*
> >
> > *Kuznetsov Aleksey*
> >
>

--

*Best Regards,*

*Kuznetsov Aleksey*