[
https://issues.apache.org/jira/browse/IGNITE-24751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Plekhanov reassigned IGNITE-24751:
------------------------------------------
Assignee: Aleksey Plekhanov
> Calcite: print warning when blocking query pool was exhausted
> -------------------------------------------------------------
>
> Key: IGNITE-24751
> URL: https://issues.apache.org/jira/browse/IGNITE-24751
> Project: Ignite
> Issue Type: Sub-task
> Reporter: Ilya Shishkov
> Assignee: Aleksey Plekhanov
> Priority: Minor
> Labels: calcite, ignite-2, ise
> Attachments: QueryPoolExhaustingTest.patch
>
>
> When {{QueryBlockingTaskExecutor}} of Calcite engine is used, query pool size
> must be larger than any UDF nesting, otherwise query hanging will occur, eg.:
> # Query executor size is 2
> # Execute SQL containing first UDF
> # First UDF inside calls SQL query with another one UDF
> # Second UDF calls any SQL query and hangs
> # Warning about long running queries are printed in the log, but they do not
> provide any information about query pool exhausting
> Reproducer: [^QueryPoolExhaustingTest.patch]
> It seems, that when {{QueryBlockingTaskExecutor}} is used we need:
> # Add detailed warning about deadlock and print information, how kill
> problematic query
> # Add documentation about proper query thread pool size configuring
> Also, for all query pools starvation check can be added, eg.: periodically
> check completed tasks count and pending queries.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
