[
https://issues.apache.org/jira/browse/IGNITE-4105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15840054#comment-15840054
]
ASF GitHub Bot commented on IGNITE-4105:
----------------------------------------
GitHub user skalashnikov opened a pull request:
https://github.com/apache/ignite/pull/1469
IGNITE-4105 Introduced separate thread pool for SQL queries
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-4105
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/1469.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1469
----
----
> 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)
