Async listeners for IgniteFuture

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Async listeners for IgniteFuture

dkarachentsev
Hello everyone!

I'm working on this ticket [1] and Vladimir made a review where he has
concerns about implementation. I want to know community opinion about
second one: where user callbacks should be processed by default?

For that purpose I used public pool for now, but this could lead to
deadlocks, so what is the best decision here: use callback fork join
pool, additional one, or maybe force user to provide his own Executor?

[1] https://issues.apache.org/jira/browse/IGNITE-4477

Thanks!

-Dmitry.

Reply | Threaded
Open this post in threaded view
|

Re: Async listeners for IgniteFuture

Taras Ledkov
Hi, Dmitry.

Is make sense use custom named executors [1] in your API?
i.e. adds method passed executor name?

[1] https://issues.apache.org/jira/browse/IGNITE-4699


On 05.04.2017 12:15, Dmitry Karachentsev wrote:

> Hello everyone!
>
> I'm working on this ticket [1] and Vladimir made a review where he has
> concerns about implementation. I want to know community opinion about
> second one: where user callbacks should be processed by default?
>
> For that purpose I used public pool for now, but this could lead to
> deadlocks, so what is the best decision here: use callback fork join
> pool, additional one, or maybe force user to provide his own Executor?
>
> [1] https://issues.apache.org/jira/browse/IGNITE-4477
>
> Thanks!
>
> -Dmitry.
>

--
Taras Ledkov
Mail-To: [hidden email]