You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Maksim Timonin (Jira)" <ji...@apache.org> on 2025/09/22 10:57:00 UTC
[jira] [Updated] (IGNITE-15365) "KILL SCAN" doesn't cancel correctly queries on remote node.
[ https://issues.apache.org/jira/browse/IGNITE-15365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maksim Timonin updated IGNITE-15365:
------------------------------------
Description:
Currently KILL SCAN just removes query iterator from node, but doesn't send cancel cache query request to every node. It leads wasting memory on nodes and exceptions like:
```
class org.apache.ignite.IgniteCheckedException: Received next page request after iterator was removed. Consider increasing maximum number of stored iterators (see CacheConfiguration.getMaxQueryIteratorsCount() configuration property).
```
see
# QueryMXBeanImpl.CancelScan
# KillComandsSQLTest#testCancelScanQuery
was:
Currently KILL SCAN just removes query iterator from node, but doesn't send cancel cache query request to every node. It leads wasting memory on nodes and exceptions like:
class org.apache.ignite.IgniteCheckedException: Received next page request after iterator was removed. Consider increasing maximum number of stored iterators (see CacheConfiguration.getMaxQueryIteratorsCount() configuration property).
see
# QueryMXBeanImpl.CancelScan
# KillComandsSQLTest#testCancelScanQuery
> "KILL SCAN" doesn't cancel correctly queries on remote node.
> ------------------------------------------------------------
>
> Key: IGNITE-15365
> URL: https://issues.apache.org/jira/browse/IGNITE-15365
> Project: Ignite
> Issue Type: New Feature
> Reporter: Maksim Timonin
> Priority: Major
>
> Currently KILL SCAN just removes query iterator from node, but doesn't send cancel cache query request to every node. It leads wasting memory on nodes and exceptions like:
> ```
> class org.apache.ignite.IgniteCheckedException: Received next page request after iterator was removed. Consider increasing maximum number of stored iterators (see CacheConfiguration.getMaxQueryIteratorsCount() configuration property).
> ```
> see
> # QueryMXBeanImpl.CancelScan
> # KillComandsSQLTest#testCancelScanQuery
--
This message was sent by Atlassian Jira
(v8.20.10#820010)