You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Chandresh Pancholi (JIRA)" <ji...@apache.org> on 2016/04/20 14:59:25 UTC
[jira] [Assigned] (IGNITE-1650) Add ability to specify thread pool
for IgniteFuture listen/chain methods.
[ https://issues.apache.org/jira/browse/IGNITE-1650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chandresh Pancholi reassigned IGNITE-1650:
------------------------------------------
Assignee: Chandresh Pancholi
> Add ability to specify thread pool for IgniteFuture listen/chain methods.
> -------------------------------------------------------------------------
>
> Key: IGNITE-1650
> URL: https://issues.apache.org/jira/browse/IGNITE-1650
> Project: Ignite
> Issue Type: Task
> Components: general
> Affects Versions: ignite-1.4
> Reporter: Vladimir Ozerov
> Assignee: Chandresh Pancholi
> Priority: Critical
> Fix For: 1.6
>
>
> Closures passed to IgniteFuture listen() and chain() methods are executed either in the same thread if future is completed, or in a completion thread (usually this is a thread from one of Ignite pools).
> This enforces restrictions on what user can do in closures. He cannot use call operations, he cannot call any Ignite operations. Otherwise deadlocks or starvation could occur.
> To fix that we should allow user to pass optional thread pool where passed closure should be executed. This already done in Java 8 CompletableFuture. We should do almost the same.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)