Hello, Igniters! I started an Ignite cluster with 12 nodes, but the cluster did not have persistence enabled.
I used 40 thin clients to listen for cache changes through continuous query function, and there were also some other thin clients constantly inserting data into the cache. When I hung up a node in the cluster using the kill command, the node quickly stopped and was pulled back up by K8S, but the node continued to restart itself. By analyzing the logs, it can be found that the cluster was kicked out due to the continuous growth of heap memory. Through analyzing the heap, I found that the reason is that the variable named backupQ in the CacheContinuousQueryEventBuffer class is occupying memory. It seems that the data in this queue is no longer deleted, but is growing infinitely. Will restarting cause this node to not receive CacheContinuousQueryBatchAck messages? Has anyone encountered this situation before? 从 Windows 版邮件发送
