[
https://issues.apache.org/jira/browse/IGNITE-4802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15924101#comment-15924101
]
ASF GitHub Bot commented on IGNITE-4802:
----------------------------------------
GitHub user vkulichenko opened a pull request:
https://github.com/apache/ignite/pull/1619
IGNITE-4802
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vkulichenko/ignite ignite-4802
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/1619.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 #1619
----
commit 5dda836176a9f24abfd132206209f365b093e775
Author: Ignite Teamcity <[email protected]>
Date: 2016-12-29T17:17:37Z
version changed to: 1.8.2
commit 2a78026be972aa923b8303600fdf6ce9c598bf76
Author: Valentin Kulichenko <[email protected]>
Date: 2017-03-14T12:36:32Z
IGNITE-4802 - Separate thread pool for services
commit c1dc94b40d1f812d46d9af165b92f46b8cd2135d
Author: Valentin Kulichenko <[email protected]>
Date: 2017-03-14T12:40:28Z
Merged from master
----
> Create separate thread pool for services
> ----------------------------------------
>
> Key: IGNITE-4802
> URL: https://issues.apache.org/jira/browse/IGNITE-4802
> Project: Ignite
> Issue Type: Improvement
> Components: managed services
> Affects Versions: 1.9
> Reporter: Valentin Kulichenko
> Assignee: Valentin Kulichenko
> Fix For: 2.0
>
>
> Currently if a service is invoked via service proxy, it will be executed on a
> remote node in its public thread pool. This means that it's unsafe to execute
> a compute job or closure from a service as it can cause starvation.
> Need to create a separate pool for services to overcome this limitation.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
