Hello! 1. In this case client will not be able to reconnect, I am afraid. You should specify several addresses there.
2. No, but the client will not be able to reconnect to a new server node until you restart. It will still be able to communicate with any new servers or clients, provided that it can access one of servers specified in configuration. 3. Yes, the simplest way is to use Multicast IP finder: https://apacheignite.readme.io/docs/tcpip-discovery#section-multicast-ip-finder There's also a wide range of IP finders there. 4. I don't think this can even remotely affect service deployment, so the reason was probably some other kind of misconfiguration as a coincidence. Regards, -- Ilya Kasnacheev вт, 16 окт. 2018 г. в 22:33, the_palakkaran <[email protected]>: > 1. How does client re-connect to another server if I have mentioned only > the > address of leader aka oldest node in its configuration? > > 2. Suppose I have mentioned all server addresses in my client's > configuration. What if I I need to add a new server node? Then I will need > to restart the client again right? > > 3. Is it possible to connect client to a cluster without mentioning ip > address of any of the nodes in the cluster in its configuration? > > 4. I faced a major challenge when I mentioned all server addresses in my > client configuration. When I deployed a service from client as cluster > singleton, it got deployed on all nodes. > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
