Failed to start cache due to conflicting cache ID

classic Classic list List threaded Threaded
3 messages Options
Sergio Hernández Martínez Sergio Hernández Martínez
Reply | Threaded
Open this post in threaded view
|

Failed to start cache due to conflicting cache ID

Hi all,

I am testing the fault tolerance of ignite 2.7 without persistence. When the ignite-0001 node goes off and gets up again, I have the following error message the other 2 nodes (ignite-0002 and ignite-0003):

2019-04-01T10: 17: 18.881 + 00: 00 ERROR - - - org.apache.ignite.logger.log4j2.Log4J2Logger {"@message": "[:] - Failed to reinitialize local partitions (rebalancing will be stopped) : GridDhtPartitionExchangeId [topVer = AffinityTopologyVersion [topVer = 5, minorTopVer = 0], diskEvt = DiscoveryEvent [evtNode = TcpDiscoveryNode [id = 2a3e4f28-8d8c-4e11-8c58-8b4385592610, addrs = [172.25.65.125], sockAddrs = [ignite-0001 .ignite.test.com / 172.25.65.125: 47500], discPort = 47500, order = 5, intOrder = 4, lastExchangeTime = 1554113838586, loc = false, ver = 2.7.0 # 20181130-sha1: 256ae401, isClient = false] , topVer = 5, nodeId8 = b329068b, msg = Node joined: TcpDiscoveryNode [id = 2a3e4f28-8d8c-4e11-8c58-8b4385592610, addrs = [172.25.65.125], sockAddrs = [ignite-0001.ignite.test.com/172.25 .65.125: 47500], discPort = 47500, order = 5, intOrder = 4, lastExchangeTime = 1554113838586, loc = false, ver = 2.7.0 # 20181130-sha1: 256ae401, isClient = false], type = NODE_JOINED, tstamp = 1554113838860 ], nodeId = 2a3e4f28, evt = NODE_JOINED] "," @ data ": {}}
org.apache.ignite.IgniteCheckedException: Failed to start cache due to conflicting cache ID (change cache name and restart grid) [cacheName = ignite-sys-cache, conflictingCacheName = ignite-sys-cache]
at org.apache.ignite.internal.processors.cache.GridCacheSharedContext.addCacheContext (GridCacheSharedContext.java:524) ~ [ignite-core-2.7.0.jar: 2.7.0]
at org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart (GridCacheProcessor.java:2161) ~ [ignite-core-2.7.0.jar: 2.7.0]
at org.apache.ignite.internal.processors.cache.GridCacheProcessor.startReceivedCaches (GridCacheProcessor.java:2063) ~ [ignite-core-2.7.0.jar: 2.7.0]
at org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init (GridDhtPartitionsExchangeFuture.java:759) [ignite-core-2.7.0.jar: 2.7.0]
at org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager $ ExchangeWorker.body0 (GridCachePartitionExchangeManager.java:2667) [ignite-core-2.7.0.jar: 2.7.0]
at org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager $ ExchangeWorker.body (GridCachePartitionExchangeManager.java:2539) [ignite-core-2.7.0.jar: 2.7.0]
at org.apache.ignite.internal.util.worker.GridWorker.run (GridWorker.java:120) [ignite-core-2.7.0.jar: 2.7.0]
at java.lang.Thread.run (Thread.java:748) [?: 1.8.0_191]

When this error occurs, the other 2 ignite nodes stop with the same error.

In the config.xml file I have the discovery is by address and I have the following to keep the same nodeid and consistenid:

       <property name = "igniteInstanceName" value = "ignite-0001" />
       <property name = "consistentId" value = "
24044899-7bec-4312-b8f2-ed204ddbc41c "/>
       <property name = "nodeId" value = "
24044899-7bec-4312-b8f2-ed204ddbc41c "/>

These parameters set them to be able to maintain my task manager.

What can be happening?

Thank you
Sergio Hernández Martínez Sergio Hernández Martínez
Reply | Threaded
Open this post in threaded view
|

RE: Failed to start cache due to conflicting cache ID

Hi all,

after remove nodeId property, every thing is working fine.

What differents are between nodeId and consistentId?

Thank you very much
SHM


De: Sergio Hernández Martínez <[hidden email]>
Enviado: lunes, 1 de abril de 2019 14:01
Para: [hidden email]
Asunto: Failed to start cache due to conflicting cache ID
 
Hi all,

I am testing the fault tolerance of ignite 2.7 without persistence. When the ignite-0001 node goes off and gets up again, I have the following error message the other 2 nodes (ignite-0002 and ignite-0003):

2019-04-01T10: 17: 18.881 + 00: 00 ERROR - - - org.apache.ignite.logger.log4j2.Log4J2Logger {"@message": "[:] - Failed to reinitialize local partitions (rebalancing will be stopped) : GridDhtPartitionExchangeId [topVer = AffinityTopologyVersion [topVer = 5, minorTopVer = 0], diskEvt = DiscoveryEvent [evtNode = TcpDiscoveryNode [id = 2a3e4f28-8d8c-4e11-8c58-8b4385592610, addrs = [172.25.65.125], sockAddrs = [ignite-0001 .ignite.test.com / 172.25.65.125: 47500], discPort = 47500, order = 5, intOrder = 4, lastExchangeTime = 1554113838586, loc = false, ver = 2.7.0 # 20181130-sha1: 256ae401, isClient = false] , topVer = 5, nodeId8 = b329068b, msg = Node joined: TcpDiscoveryNode [id = 2a3e4f28-8d8c-4e11-8c58-8b4385592610, addrs = [172.25.65.125], sockAddrs = [ignite-0001.ignite.test.com/172.25 .65.125: 47500], discPort = 47500, order = 5, intOrder = 4, lastExchangeTime = 1554113838586, loc = false, ver = 2.7.0 # 20181130-sha1: 256ae401, isClient = false], type = NODE_JOINED, tstamp = 1554113838860 ], nodeId = 2a3e4f28, evt = NODE_JOINED] "," @ data ": {}}
org.apache.ignite.IgniteCheckedException: Failed to start cache due to conflicting cache ID (change cache name and restart grid) [cacheName = ignite-sys-cache, conflictingCacheName = ignite-sys-cache]
at org.apache.ignite.internal.processors.cache.GridCacheSharedContext.addCacheContext (GridCacheSharedContext.java:524) ~ [ignite-core-2.7.0.jar: 2.7.0]
at org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart (GridCacheProcessor.java:2161) ~ [ignite-core-2.7.0.jar: 2.7.0]
at org.apache.ignite.internal.processors.cache.GridCacheProcessor.startReceivedCaches (GridCacheProcessor.java:2063) ~ [ignite-core-2.7.0.jar: 2.7.0]
at org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init (GridDhtPartitionsExchangeFuture.java:759) [ignite-core-2.7.0.jar: 2.7.0]
at org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager $ ExchangeWorker.body0 (GridCachePartitionExchangeManager.java:2667) [ignite-core-2.7.0.jar: 2.7.0]
at org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager $ ExchangeWorker.body (GridCachePartitionExchangeManager.java:2539) [ignite-core-2.7.0.jar: 2.7.0]
at org.apache.ignite.internal.util.worker.GridWorker.run (GridWorker.java:120) [ignite-core-2.7.0.jar: 2.7.0]
at java.lang.Thread.run (Thread.java:748) [?: 1.8.0_191]

When this error occurs, the other 2 ignite nodes stop with the same error.

In the config.xml file I have the discovery is by address and I have the following to keep the same nodeid and consistenid:

       <property name = "igniteInstanceName" value = "ignite-0001" />
       <property name = "consistentId" value = "
24044899-7bec-4312-b8f2-ed204ddbc41c "/>
       <property name = "nodeId" value = "
24044899-7bec-4312-b8f2-ed204ddbc41c "/>

These parameters set them to be able to maintain my task manager.

What can be happening?

Thank you
ibelyakov ibelyakov
Reply | Threaded
Open this post in threaded view
|

RE: Failed to start cache due to conflicting cache ID

Hi,

Seems like "nodeId" is deprecated property and "consistentId" should be used
instead of it.

Javadoc:
https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/configuration/IgniteConfiguration.html#getNodeId--

Regards,
Igor



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