Apache ignite node won't join cluster if server nodes start simultaneously

Question

We have a problem with ignite when we start two ignite server nodes at the exact same time. We are currently implementing our own discovery mechanism by extending TcpDiscoveryIpFinderAdapter. The first time the TcpDiscoveryIpFinderAdapter is called neither ignite servers will be able to find the other node (due to the nature of our discovery mechanism). Subsequent invocations does report the other node with a correct IP, yet the ignite nodes will not start to talk to each other.

If we start the servers with some delay, the second server will (on the first attempt) find the other node and join the cluster successfully.

Is there a way to get the two nodes to talk to each other even after both of them initially think they are a cluster of one node?

Emera

No, there is no way to "merge" two clusters of single nodes into a cluster of two nodes. You should fix this at the level of IP finder implementation. If you need more assistance on this I would recommend you sending this question to Ignite dev list. Also are you sure you need to implement your own IP finder? There are plenty of them available out of the box apacheignite.readme.io/docs/cluster-config – Speak

Thank you for the info. We are using Eureka as a service discovery for other services which is why we're implementing our own IP-finder. – Emera

Do you mean this library under Eureka? github.com/Netflix/eureka If so probably for you it will be enough to use AWS IP finder or JClouds IP finder. apacheignite.readme.io/v1.6/docs/aws-config apacheignite.readme.io/docs/generic-cloud-configuration – Speak

duplicates #58445437 – Ailurophobe

for similar issue in k8s see https://mcmap.net/q/1629747/-ignite-readinessprobe – Ailurophobe