Critical System Error in ContinuousQuery processing node

Hi, When I start a continuous query listener while another client is deleting entries from the same cache, I observe the node and listener crash with this exception in the node: err=java.lang.ClassCastException: java.lang.Object cannot be cast to java.util.List at org.apache.ignite.internal.pro

Recall: Ignite node crash

Lo, Marcus [ICG-IT] would like to recall the message, "Ignite node crash".

Ignite 2.10.0 client "Node_Failed" during application pool recycle

Hi Ignite team, We are using Ignite 2.10.0 with .Net 5 WebAPI and we have a 16-nodes(2 servers) Ignite cluster The client nodes have the following property as below IgniteConfiguration.AutoGenerateIgniteInstanceName = true; IgniteConfiguration.ConsistentId = Guid.NewGuid().ToString().ToUpper(); So

Use S3 as persistent Store for ignite caches

Hi, Asking further queries on this post here. Is it possible to use S3 as backend persistent store for ignite caches. We are exploring options to backup and restore data into ignite. 2.11.x snapshots don't support incremental backups and PITR. https://stackoverflow.com/questions/70875613/back-and

Re: Ignite node crash

Hi, at first glance you really have a network problems, check 04c.log : 2022-01-25 18:32:53.858+ WARN [grid-nio-worker-tcp-comm-2-#25%TcpCommunicationSpi%] o.a.i.s.c.t.TcpCommunicationSpi          : Communication SPI session write timed out (consider increasing 'socketWriteTimeout' configur

Re: Ignite 2.10.0 client "Node_Failed" during application pool recycle

Hi Charlin, ConsistentId should not be random [1] 1. Is there a reason to set it manually? 2. Do you use Ignite persistence? [1] https://ignite.apache.org/docs/latest/persistence/native-persistence On Fri, Jan 28, 2022 at 6:53 AM Charlin S wrote: > Hi Ignite team, > We are using Ignite 2.10.0