Mailing-List: contact issues-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
Date: Mon, 3 Apr 2017 07:45:41 +0000 (UTC)
From: "Dmitry Karachentsev (JIRA)" <jira@apache.org>
To: issues@ignite.apache.org
Message-ID: <JIRA.13030076.1482403074000.188805.1491205541661@Atlassian.JIRA>
In-Reply-To: <JIRA.13030076.1482403074000@Atlassian.JIRA>
References: <JIRA.13030076.1482403074000@Atlassian.JIRA> <JIRA.13030076.1482403074983@jira-lw-us.apache.org>
Subject: [jira] [Commented] (IGNITE-4477) Fix IgniteFuture.listen() and
 IgniteFuture.chain() semantics
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 03 Apr 2017 07:45:46 -0000


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

Dmitry Karachentsev commented on IGNITE-4477:
---------------------------------------------

Vladimir, please review the fix: [PR 1710|https://github.com/apache/ignite/pull/1710]

Instead of two async methods for listen and chain I've added one with nullable Executor. I don't think we need to duplicate methods just without last argument.

> Fix IgniteFuture.listen() and IgniteFuture.chain() semantics
> ------------------------------------------------------------
>
>                 Key: IGNITE-4477
>                 URL: https://issues.apache.org/jira/browse/IGNITE-4477
>             Project: Ignite
>          Issue Type: Task
>          Components: general
>    Affects Versions: 1.8
>            Reporter: Vladimir Ozerov
>            Assignee: Dmitry Karachentsev
>             Fix For: 2.0
>
>
> *Problem*
> We allow users to pass continuations to {{IgniteFuture}} which will be executed on future completion. This can be done through {{listen}} or {{chain}} methods.
> However, continuation semantics is broken intrinsically:
> 1) If future is already completed, user code executed in the same thread;
> 2) If future is not completed yet, it will be executed in completion thread.
> Neither of this options are valid because it easily leads to starvation. E.g.:
> {code}
> IgniteFuture fut = cache.getAsync(key2);
> fut.listen(fut0 -> {
>      cache.put(key2, val2); // Possible deadlock, because invoked in sys pool;
> });
> {code}
> *Solution*
> 1) By default callbacks must be executed asynchronously in some common pool (public pool? new "callback pool"? FJP?)
> 2) It should be possible to specify where to execute a callback explicitly:
> {code}
> IgniteFuture.listen(IgniteClosure, ExecutorService);
> {code}
> 3) We may want to expose our public pool on API for convenience.


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)