[
https://issues.apache.org/jira/browse/IGNITE-11456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16811637#comment-16811637
]
Ignite TC Bot commented on IGNITE-11456:
----------------------------------------
{panel:title=--> Run :: All: No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3514596&buildTypeId=IgniteTests24Java8_RunAll]
> Use separate pool for KILL QUERY command
> ----------------------------------------
>
> Key: IGNITE-11456
> URL: https://issues.apache.org/jira/browse/IGNITE-11456
> Project: Ignite
> Issue Type: Task
> Components: sql
> Reporter: Yury Gerzhedovich
> Assignee: Yury Gerzhedovich
> Priority: Major
> Labels: iep-29
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> As of now we use QUERY_POOL to process cancellation requests. It can lead to
> unable to cancel a queries in case the pool will be overflowed.
> So, need to use separate pool or MGMT pool + non-blocking processing through
> futures.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
