Re: Only one node has a high number of SystemExecutor CompletedTask

Thanks to your kind reply. We use Ignite to Group By Query about time series data. However, I have seen a lot of data, so when I create TimeWindow through Expiry Strategy in one cache, I see that it uses too many resources to expire entries. As a result, I have adopted a method of simply destroy

Re: Only one node has a high number of SystemExecutor CompletedTask

Hi as you already noted, ignite cluster has a special node - coordinator, the oldest node in a cluster is coordinator node: ignite.cluster().forServers().forOldest().node() In case of creation/destroying a cache, coordinator needs to coordinate this process and notify each node about cache crea

Re: Only one node has a high number of SystemExecutor CompletedTask

I found something that could be a clue. The node exposed by ignite.cluster().forServers().forOldest().node() seems to be a problem. Do you have any expectations? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Only one node has a high number of SystemExecutor CompletedTask

The pattern we use is a structure that periodically creates and destroys Cache. At this point, could a particular node not be able to clean up the heap? -- Sent from: http://apache-ignite-users.70518.x6.nabble.co

Only one node has a high number of SystemExecutor CompletedTask

Hi, team. I have a problem about cluster cpu usage. Ignite Cluster is running on 10 nodes. Unusually, only one node has a high number of SystemExecutor and CPU utilization and Minor GC time are higher than other nodes. Is there a separate role between the nodes, so that one node becomes the coo