[ 
https://issues.apache.org/jira/browse/IGNITE-13059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17113871#comment-17113871
 ] 

Vyacheslav Koptilin commented on IGNITE-13059:
----------------------------------------------

Hi [~manueltg89],

 

It looks like the issue is already resolved. Please take a look at IGNITE-12805
You can try using 2.8.1 RC (which will be released soon), for instance, in 
order to be sure that the issue has gone.

Dev list discussion related to 2.8.1 
[http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-2-8-1-RELEASE-Time-Scope-Manager-td46452.html]

 

Thanks,
S.

> When I activate write-behind with RDBMS Ignite isn't starting
> -------------------------------------------------------------
>
>                 Key: IGNITE-13059
>                 URL: https://issues.apache.org/jira/browse/IGNITE-13059
>             Project: Ignite
>          Issue Type: Bug
>          Components: cache
>    Affects Versions: 2.8
>         Environment: Microsoft Windows 10
> Apache Ignite 2.8
> MariaDB 10.2
>            Reporter: Manuel
>            Assignee: Vyacheslav Koptilin
>            Priority: Critical
>              Labels: Ignite, MySQL, RDBMS, cache, store, write-behind
>         Attachments: ImportedCluster3-project (2).zip
>
>
> I 've created a Ignite application for "Automatic RDBMS Support" with version 
> 2.8 and when I activate write-behind functionality the Ignite cluster isn't 
> working, but, with version 2.7 works perfectly. If I put write-behind to 
> false then the app is works correctly.  The error is:
> {code:java}
> // marcador de posición de código
> GRAVE: Exception during start processors, node will be stopped and close 
> connectionsGRAVE: Exception during start processors, node will be stopped and 
> close connectionsjava.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:330)
>  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) at 
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2038)
>  at 
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1703)
>  at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1117) at 
> org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:637) at 
> org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:563) at 
> org.apache.ignite.Ignition.start(Ignition.java:321) at 
> startup.ServerNodeCodeStartup.main(ServerNodeCodeStartup.java:16){code}
> {code:java}
> may 22, 2020 9:50:35 AM org.apache.ignite.logger.java.JavaLogger errorGRAVE: 
> Got exception while starting (will rollback startup 
> routine).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:330)
>  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) at 
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2038)
>  at 
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1703)
>  at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1117) at 
> org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:637) at 
> org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:563) at 
> org.apache.ignite.Ignition.start(Ignition.java:321) at 
> startup.ServerNodeCodeStartup.main(ServerNodeCodeStartup.java:16)
> {code}
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to