AW: NullPointer in GridAffinityAssignment.initPrimaryBackupMaps

IGNITE_HOME = null is usually no problem. What and how should I set? I use Ignite in embedded mode... Lukas Lentner, B. Sc. St.-Cajetan-Straße 13 81669 München Deutschland Fon: +49 / 89 / 44 38 61 27 Mobile: +49 / 176 / 24 77 09 22 E-Mail: kont...@lukaslentner.de Website

Prohibit "Node is out of topology"

now how to circumvent these failing nodes in future. What could be the reason for such a node segmentation. As this runs on AWS and we even see a similar error when the nodes are running on the same vm I am pretty sure it is NOT a network issue ... Thankx Lukas ---- Lukas Lentner, B. Sc. St.-Cajetan

AW: Ignite and Memory Info

Begin or end ? ;-)) 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: kont...@lukaslentner.de Website: www.LukasLentner.de IBAN:DE33 7019 0001 1810 17 BIC: GENODEF1M01 (Münchner

AW: Ignite and Memory Info

You wrote in the post before that it could go into 2.1 … My question is: When will 2.1 come and will it be in there … ;-) Bye Lukas 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: kont

AW: Ignite and Memory Info

Hi, what is date of the fixed version? Thankx Lukas 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: kont...@lukaslentner.de Website: www.LukasLentner.de IBAN:DE33 7019 0001 1810 17

AW: Ignite and Memory Info

Is there any possible workaround? It pretty much makes me unable to use ignite right now… It is a real dealbreaker ;-)) 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: kont...@lukaslentner.de

Ignite and Memory Info

sue tracker as netbeans, ... and my impression is, that it is common. So GridDiscoveryManager should think about the possibility to get such error and not kill the whole process because of it. What do you think? Do you have the same error sometimes? Bye Lukas ---- Lukas Lentner, B. Sc. St.-Caje

AW: Network Discovery inside docker containers

Ok, I heard from chat that I should use an https://ignite.apache.org/releases/1.8.0/javadoc/org/apache/ignite/configuration/BasicAddressResolver.html ADDRESS Resolver. I will look into it. Thankx Lukas Lukas Lentner, B. Sc. St.-Cajetan-Straße 13 81669 München Deutschland Fon: +49

Network Discovery inside docker containers

e table? It is not about retrieving the machine ip. At all times I have that! Thankx Lukas 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: kont...@lukaslentner.de Website: www.LukasLentner.de

AW: AW: AW: AW: Rediscovery after Startup

Thankx. That did it! 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: kont...@lukaslentner.de Website: www.LukasLentner.de IBAN:DE41 7019 0002 1125 58 BIC: GENODEF1M01

Connection problems

f66f702de2482466dce954d570a8ccf2 >>> stopped OK >>> +-----+ >>> Grid uptime: 00:01:33:365 Lukas Lentner, B. Sc. St.-Cajetan-Straße 13 81669 München Deutschland Fon: +49 / 89 / 71 67 44 96 Mobile: +49 / 176 / 24 7

AW: AW: AW: Rediscovery after Startup

one... ---- 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: kont...@lukaslentner.de Website: www.LukasLentner.de IBAN:DE41 7019 0002 1125 58 BIC: GENODEF1M01 (Münchner Bank) > -Ursprün

AW: AW: Rediscovery after Startup

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 ...

AW: Rediscovery after Startup

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

Rediscovery after Startup

Hi, can somebody please tell me how to force an ignite node programmatically to again try to discover other nodes it did not find at the startup process. I use: final TcpDiscoveryVmIpFinder ipFinder = new TcpDiscoveryVmIpFinder(); ipFinder.setShared(true); ipFinder.setAddresses(this