[
https://issues.apache.org/jira/browse/IGNITE-28483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Orlov updated IGNITE-28483:
--------------------------------------
Fix Version/s: 3.2
> Sql. Simplify close method in DistributedQueryManager
> -----------------------------------------------------
>
> Key: IGNITE-28483
> URL: https://issues.apache.org/jira/browse/IGNITE-28483
> Project: Ignite
> Issue Type: Improvement
> Components: sql ai3
> Reporter: Konstantin Orlov
> Assignee: Konstantin Orlov
> Priority: Major
> Labels: ignite-3
> Fix For: 3.2
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently, this method first build execution chain, and then starts execution
> in a separate thread pool. But synchronous part is in fact really small: it
> basically schedules the closing task for every local fragment.
> The problem is that this method is on hot path, and introduces one
> unnecessary thread switch, which in turn may affect latency in certain
> scenarios.
> Second problem with this method is that it sends `queryCloseMessage`
> unconditionally back to coordinator node. Need to take closer look and
> probably get rid of this.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
