(Münchner Bank)
> -Ursprüngliche Nachricht-
> Von: vkulichenko [mailto:valentin.kuliche...@gmail.com]
> Gesendet: Mittwoch, 11. Januar 2017 23:50
> An: user@ignite.apache.org
> Betreff: Re: AW: AW: AW: Rediscovery after Startup
>
> I just noticed that you set ipFinder.s
I just noticed that you set ipFinder.setShared(true); which actually causing
this behavior. If you remove this line, B will wait for A in your case, as I
described before.
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Rediscovery-after-Startup-tp10007p100
gliche Nachricht-
> Von: vkulichenko [mailto:valentin.kuliche...@gmail.com]
> Gesendet: Mittwoch, 11. Januar 2017 01:27
> An: user@ignite.apache.org
> Betreff: Re: AW: AW: Rediscovery after Startup
>
> If node can't connect to any of the addresses, and can't bind
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
So it is not possible what I ask for? In my setup there is a reason why this
node knows this IP and not the other way around ...
Lukas,
New node connects to the one that is already running, not other way around.
Actually, for node to start it must be able to connect to one of the
addresses in the IP finder, OR be able to bind to one of these addresses. So
the fact that your node started means that its own address was provi
Hi,
yea the node is started and the only one in the topology. But It tries to
discover 172.17.0.5 without luck. Now when 172.17.0.5 is available I would like
to try to launch the discover-process again after the startup process. How can
I achieve this?
I turned on DEBUG-logging on purpose!
By
