ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From vkulichenko <valentin.kuliche...@gmail.com>
Subject Re: Distributed Closures VS Executor Service
Date Tue, 28 Mar 2017 19:26:12 GMT
kmandalas wrote*
> One question is
> : if some Job fails and other Jobs belonging to the same Task are still
> running (in the same or other grid nodes), is it possible to cancel them
> and abort the whole Task before waiting for all of them to finish?

This will happen if result() method throws an exception.

kmandalas wrote*
> Another question is
> : now, since we need Spring beans to be instantiated and available at all
> participating grid nodes, we do not have the option to start Ignite at
> each node of the cluster by using ignite.sh right? We will need to start
> web server and deploy the web-app everywhere with it's Spring application
> context utilizing IgniteSpringBean.

You can use ignite.sh with Spring XML file. It will automatically find
IgniteConfiguration bean to start Ignite with, and will also make the whole
application context available to Ignite.


View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Distributed-Closures-VS-Executor-Service-tp11192p11519.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

View raw message