[
https://issues.apache.org/jira/browse/IGNITE-15365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18029597#comment-18029597
]
Maksim Timonin edited comment on IGNITE-15365 at 10/13/25 7:18 PM:
-------------------------------------------------------------------
Some notes:
1. Found that the message "Received next page request after iterator was
removed" is called because cancelling through QueryMXBeanImpl ignores
`GridCacheDistributedQueryManager#cancelIds` collection. See
`GridCacheDistributedQueryManager#processQueryRequest`.
2. Added call of the function directly, but in this case the test iterator
hangs.
3. AFAIU, Ignite should close resources for iterator in
`GridCacheQueryManager#removeQueryResult`.
[~korotm] Please, investigate why iterator close in this case.
was (Author: timonin.maksim):
Some notes:
1. Found that the message "Received next page request after iterator was
removed" is called because cancelling through QueryMXBeanImpl ignores
`GridCacheDistributedQueryManager#cancelIds` collection. See
`GridCacheDistributedQueryManager#processQueryRequest`.
2. Added call of the function directly, but in this case the test iterator
hangs.
3. AFAIU, Ignite should close resources for iterator in
`GridCacheQueryManager#removeQueryResult`.
Please, investigate why iterator close in this case.
> "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
> Assignee: Mikhail Korotkov
> 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:
>
> {code:java}
> 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).
>
> {code}
> see
> # QueryMXBeanImpl.CancelScan
> # KillComandsSQLTest#testCancelScanQuery
>
> example of test can be found in KillCommandsMXBeanTest
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
