Re: Failed to wait for initial partition map exchange

2018-09-12 Thread ndipiazza3565
No. Persistence is disabled in my case. 



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


Re: Failed to wait for initial partition map exchange

2018-09-12 Thread ndipiazza3565
I'm trying to build up a list of possible causes for this issue.

I'm only really interested in the issues that occur after successful
production deployments. Meaning the environment has been up for some time
successfully, but then later on our ignite nodes will not start and stick 

But as of now, a certain bad behavior from a single node in the ignite
cluster can cause a deadlock 

* Anything that causes one of the ignite nodes to become unresponsive 
  * oom
  * high gc
  * high cpu
  * high disk usage
* Network issues?

I'm trying to get a list of the causes for this issue so I can troubleshoot
further. 



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


How do you fix affinity key backups in cache configuration?

2017-10-23 Thread ndipiazza3565
Was just hit with this error causing my whole ignite cluster to fail to
start:

org.apache.ignite.IgniteCheckedException: Affinity key backups mismatch (fix
affinity key backups in cache configuration or set
-DIGNITE_SKIP_CONFIGURATION_CONSISTENCY_CHECK=true system property)
[cacheName=ignite-atomics-sys-cache, localAffinityKeyBackups=1,
remoteAffinityKeyBackups=0, rmtNodeId=d663345e-x7ba-5c85-6144-1234a7d3f721]
at
org.apache.ignite.internal.processors.cache.GridCacheUtils.checkAttributeMismatch(GridCacheUtils.java:1144)
~[ignite-core-1.7.0.jar:1.7.0]
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.checkCache(GridCacheProcessor.java:2915)
~[ignite-core-1.7.0.jar:1.7.0]
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.onKernalStart(GridCacheProcessor.java:756)
~[ignite-core-1.7.0.jar:1.7.0]
at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:930)
[ignite-core-1.7.0.jar:1.7.0]
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1739)
[ignite-core-1.7.0.jar:1.7.0]
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1589)
[ignite-core-1.7.0.jar:1.7.0]
at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1042)
[ignite-core-1.7.0.jar:1.7.0]
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:569)
[ignite-core-1.7.0.jar:1.7.0]
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:516)
[ignite-core-1.7.0.jar:1.7.0]
at org.apache.ignite.Ignition.start(Ignition.java:322)
[ignite-core-1.7.0.jar:1.7.0]

What does it mean by "fix affinity key backups in cache configuration" ? 



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