You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2017/01/27 09:19:24 UTC

[jira] [Comment Edited] (IGNITE-4105) Create separate thread pool for SQL queries.

    [ https://issues.apache.org/jira/browse/IGNITE-4105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15842393#comment-15842393 ] 

Vladimir Ozerov edited comment on IGNITE-4105 at 1/27/17 9:19 AM:
------------------------------------------------------------------

Sergey, my comments:
1) Test was not reliable - relying to thread name is bad practice. I reworked it to policy checks.
2) Please remove {{sql}} prefix. We creating pool for queries, not for SQL queries.
3) {{IgniteSqlQueryDedicatedPoolTest}} is not added to query suite.


was (Author: vozerov):
Andrew, my comments:
1) Test was not reliable - relying to thread name is bad practice. I reworked it to policy checks.
2) Please remove {{sql}} prefix. We creating pool for queries, not for SQL queries.
3) {{IgniteSqlQueryDedicatedPoolTest}} is not added to query suite.

> Create separate thread pool for SQL queries.
> --------------------------------------------
>
>                 Key: IGNITE-4105
>                 URL: https://issues.apache.org/jira/browse/IGNITE-4105
>             Project: Ignite
>          Issue Type: Task
>          Components: SQL
>    Affects Versions: 1.7
>            Reporter: Vladimir Ozerov
>            Assignee: Sergey Kalashnikov
>            Priority: Critical
>             Fix For: 2.0
>
>
> If several long-running queries are executed, all concurrent cache operations will be blocked because there will be no threads in system pool to server cache requests/responses.
> Let's introduce separate thread pool for SQL queries execution.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)