Apache Ignite cluster node events Not Triggered.

[BASAVARAJ BASAVARAJ <ba...@greytip.com>]

Hi,

working with ignite with kubernetes ipfinder

org.apache.ignite.spi.discovery.tcp.ipfinder.kubernetes.TcpDiscoveryKubernetesIpFinder

in local machine i have started 2 local server instance with IP finder..

org.apache.ignite.spi.discovery.tcp.ipfinder.multicast.TcpDiscoveryMulticastIpFinder

and i have registered local listener for events

ignite.events().localListen(evt -> {},EventType.EVTS_DISCOVERY);

in local machine if local server stopped, ignite EVT_NODE_LEFT will
trigger. if all server node left EVT_CLIENT_NODE_DISCONNECTED event will
trigger.

but in testing server with kubernetes IP finder if i stopped all pods in
which ignite is running there no ignite event triggering
CLIENT_NODE_DISCONNECTED.

but if restart ignite pods then the previous CLIENT_NODE_DISCONNECTED event
triggered after that CLIENT_NODE_RECONNECTING,NODE_JOIN event is triggered.

need some suggestion why event CLIENT_NODE_DISCONNECTED is not trigger once
pods stopped and why CLIENT_NODE_DISCONNECTED event is triggered after pods
are up,is there any queue if pods get down.



-- 

Thanks and regards,

Basavaraj | Software Engineer
Tel: +91 80 4022 5900 (Ext. 209)
Mob: +91 9886283409

<http://www.greythr.com/?utm_source=signature&utm_medium=greythr>

*Confidentiality Note:* This e-mail and any attachments are confidential
and may be protected by legal privilege. If you are not the intended
recipient, be aware that any disclosure, copying, distribution or use of
this e-mail or any attachment is prohibited. If you have received this
e-mail in error, please notify us immediately by returning it to the sender
and delete this copy from your system. Thank you for your cooperation.