I have 2 server nodes A and B. Because of my setup only B knows the IP address of A not vice-versa. But B starts first. So while starting B tries to contact A (discovery) but does not reach it.
Then after a while A becomes available. A does not know anything about B. I wish now that B by itself tries to discover A again (as while starting). My experience is that B just tries once at the beginning and not afterwards => How can I change this? I wish that the discovery-process of node B goes on and on, but right now it stops after the first fail and feels happy being alone... ---- Lukas Lentner, B. Sc. St.-Cajetan-Straße 13 81669 München Deutschland Fon: +49 / 89 / 71 67 44 96 Mobile: +49 / 176 / 24 77 09 22 E-Mail: [email protected] Website: www.LukasLentner.de IBAN: DE41 7019 0000 0002 1125 58 BIC: GENODEF1M01 (Münchner Bank) > -----Ursprüngliche Nachricht----- > Von: vkulichenko [mailto:[email protected]] > Gesendet: Mittwoch, 11. Januar 2017 01:27 > An: [email protected] > Betreff: Re: AW: AW: Rediscovery after Startup > > If node can't connect to any of the addresses, and can't bind to any of the > addresses, it will actually wait and will join once someone is started. I > probably do not understand the problem, please explain in more detail. > > -Val > > > > -- > View this message in context: http://apache-ignite- > users.70518.x6.nabble.com/Rediscovery-after-Startup-tp10007p10014.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com.
