You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Yury Gerzhedovich (JIRA)" <ji...@apache.org> on 2019/03/19 09:31:00 UTC
[jira] [Assigned] (IGNITE-11456) Use separate pool for KILL QUERY
command
[ https://issues.apache.org/jira/browse/IGNITE-11456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yury Gerzhedovich reassigned IGNITE-11456:
------------------------------------------
Assignee: Yury Gerzhedovich
> 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
>
>
> 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)