Re: AW: NullPointer in GridAffinityAssignment.initPrimaryBackupMaps

2017-11-15 Thread Alexey Popov
Lukas,

You are right, IGNITE_HOME could not be a problem in embedded mode.

Do you have any specific Affinity Function parameters in Cache
configuration?

Thanks,
Alexey



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/


AW: NullPointer in GridAffinityAssignment.initPrimaryBackupMaps

2017-11-14 Thread Lukas Lentner
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: www.LukasLentner.de

IBAN:DE33 7019  0001 1810 17
BIC: GENODEF1M01 (Münchner Bank)

> -Ursprüngliche Nachricht-
> Von: Alexey Popov [mailto:tank2.a...@gmail.com]
> Gesendet: Dienstag, 14. November 2017 09:03
> An: user@ignite.apache.org
> Betreff: Re: NullPointer in GridAffinityAssignment.initPrimaryBackupMaps
> 
> Hi Lukas,
> 
> It seems that a new node is just misconfigured and it can't correctly assign
> partitions by Affinity Function.
> 
> Please set a valid IGNITE_HOME and verify that Affinity Function [1] matches
> the cluster config
> 
> 2017-11-11 06:10:34:973 + [main] INFO
> org.apache.ignite.internal.IgniteKernal - IGNITE_HOME=null
> 
> [1]
> https://apacheignite.readme.io/docs/affinity-collocation#section-affinity-
> function
> 
> Thanks,
> Alexey
> 
> 
> 
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/