Apache Ignite cluster node events

8/28/2019

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.

-- Basavaraj
ignite
kubernetes

0 Answers