Hello! I can see there is a previous occurrence of this issue: http://apache-ignite-users.70518.x6.nabble.com/NullPointerException-in-GridDhtPartitionDemander-td19010.html
Can you elaborate what is your topology version and actual Ignite version? Maybe you can find anything else in server logs? Regards, -- Ilya Kasnacheev пн, 20 янв. 2020 г. в 16:40, userx <[email protected]>: > hi team, > > I recently observed an error bringing down one of the ignite server nodes. > The log mentions a NullPointerExceptionException on preload of an entry. > Subsequently 2 other nodes went down. Here is the stack trace of first > failure > > 2019-12-14 06:47:51,030 ERROR [sys-#61006%ABCD4%] {} > org.apache.ignite.internal.processors.cache.GridCacheIoManager - > Failed processing message > [ > senderId=647bc0f2-67d8-469b-9a49-af4231463887, > msg=GridDhtPartitionSupplyMessage > [ > rebalanceId=117004, > topVer=AffinityTopologyVersion > [ > topVer=67, > minorTopVer=395 > ], > missed=null, > clean=null, > msgSize=524366, > estimatedKeysCnt=-1, > size=1, > parts=[449], > super=GridCacheGroupIdMessage [grpId=1152451571] > ] > ] > java.lang.NullPointerException > at > > org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionDemander.preloadEntry(GridDhtPartitionDemander.java:893) > at > > org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionDemander.handleSupplyMessage(GridDhtPartitionDemander.java:772) > at > > org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader.handleSupplyMessage(GridDhtPreloader.java:387) > at > > org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$5.apply(GridCachePartitionExchangeManager.java:419) > at > > org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$5.apply(GridCachePartitionExchangeManager.java:409) > at > > org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1056) > at > > org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:581) > at > > org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$700(GridCacheIoManager.java:101) > at > > org.apache.ignite.internal.processors.cache.GridCacheIoManager$OrderedMessageListener.onMessage(GridCacheIoManager.java:1613) > at > > org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1569) > at > > org.apache.ignite.internal.managers.communication.GridIoManager.access$4100(GridIoManager.java:127) > at > > org.apache.ignite.internal.managers.communication.GridIoManager$GridCommunicationMessageSet.unwind(GridIoManager.java:2768) > at > > org.apache.ignite.internal.managers.communication.GridIoManager.unwindMessageSet(GridIoManager.java:1529) > at > > org.apache.ignite.internal.managers.communication.GridIoManager.access$4400(GridIoManager.java:127) > at > > org.apache.ignite.internal.managers.communication.GridIoManager$10.run(GridIoManager.java:1498) > at > > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at > > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > > > 1) The question is that in spite of the fixed number of Ignite server > nodes, > why is the rebalance triggered ? > 2) What is causing the Null pointer ? > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
