Hi, We noticed whenever long running queries fired, nodes are going out of topology and entire ignite cluster is down.
In my case, a filter criteria could get 5L records. So each API request could fetch 250 records. When page number is getting increased the query execution time is high and entire cluster is down https://issues.apache.org/jira/browse/IGNITE-4003 related to this ? Can we set seperate thread pool for queries executions, compute jobs and other services instead of common public thread pool ? Thanks
