Adam Wiedel created IGNITE-14627:
------------------------------------
Summary: Ignite fails before able to activate cluster
Key: IGNITE-14627
URL: https://issues.apache.org/jira/browse/IGNITE-14627
Project: Ignite
Issue Type: Bug
Environment: I'm running in a CentOS Docker image using Ignite 2.8.
The only change in my configuration was adding the data storage configuration.
<beans xmlns="http://www.springframework.org/schema/beans";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd";>
<bean id="servicesDataStorageConfig"
class="org.apache.ignite.configuration.DataStorageConfiguration">
<property name="storagePath" value="#\{ systemEnvironment['PROJECT_HOME']
}/grid/services/storage" />
<property name="walPath" value="#\{ systemEnvironment['PROJECT_HOME']
}/grid/services/wal" />
<property name="walArchivePath" value="#\{ systemEnvironment['PROJECT_HOME']
}/grid/services/wal/archive" />
<property name="defaultDataRegionConfiguration">
<bean class="org.apache.ignite.configuration.DataRegionConfiguration">
<property name="name" value="SERVICES_DEFAULT_REGION" />
<property name="initialSize" value="#\{128 * 1024 * 1024}" />
<property name="persistenceEnabled" value="true" />
</bean>
</property>
<property name="dataRegionConfigurations">
<list>
<bean class="org.apache.ignite.configuration.DataRegionConfiguration">
<property name="name" value="SERVICES_PERSISTENCE_REGION" />
<property name="initialSize" value="#\{512 * 1024 * 1024}" />
<property name="maxSize" value="#\{1024 * 1024 * 1024}" />
<property name="persistenceEnabled" value="true" />
</bean>
</list>
</property>
</bean>
</beans>
Reporter: Adam Wiedel
I'm starting my nodes within Docker containers that I have created using the
"ignite.sh" script that is deployed within the image. Recently, I turned on
native persistence for my default data region configuration, and now the node
fails to start with this exception:
_Caused by: java.lang.NullPointerException_
_at
org.apache.ignite.internal.processors.cache.GridCacheUtils.affinityNode(GridCacheUtils.java:1374)_
_at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$CachePredicate.dataNode(GridDiscoveryManager.java:3205)_
_at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.cacheAffinityNode(GridDiscoveryManager.java:1894)_
_at
org.apache.ignite.internal.processors.cache.ValidationOnNodeJoinUtils.validate(ValidationOnNodeJoinUtils.java:346)_
_at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.createCacheContext(GridCacheProcessor.java:1201)_
_at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCacheInRecoveryMode(GridCacheProcessor.java:2291)_
_at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.access$1700(GridCacheProcessor.java:202)_
_at
org.apache.ignite.internal.processors.cache.GridCacheProcessor$CacheRecoveryLifecycle.afterBinaryMemoryRestore(GridCacheProcessor.java:5387)_
_at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.restoreBinaryMemory(GridCacheDatabaseSharedManager.java:1075)_
_at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.startMemoryRestore(GridCacheDatabaseSharedManager.java:2068)_
_at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1254)_
It seems like I should be able to start the node and have time to activate the
cluster before it fails.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
