Sorry for polluting the mailing list.

Ignition.stop(false); // internally stops / cancels the local Ignite service.

Can anyone answer for the 2nd question?


On Mon, Jul 11, 2016 at 10:00 AM, Kamal C <> wrote:

I've applied your suggestion. Still, Ignite closes the service running in all the nodes,

ClusterGroup grp = ignite.cluster().forNode(ignite.cluster().localNode());;


class org.apache.ignite.IgniteException: Failed to find deployed service: CalcService
    at org.apache.ignite.internal.processors.service.GridServiceProxy.invokeMethod(
    at org.apache.ignite.internal.processors.service.GridServiceProxy$ProxyInvocationHandler.invoke(
    at com.sun.proxy.$Proxy28.add(Unknown Source)
    at my.apache.ignite.examples.servicegrid.ServiceDeployer.useService(

Re-framing my question:

-  Is Service.cancel() method is not a appropriate place for resource cleanups on shutdown?
-  How to tell Ignite to move a clustered singleton service from one node to another with external scripts?

-- Kamal

On Sat, Jul 9, 2016 at 1:07 AM, Vladislav Pyatkov <> wrote:
Hello Kamal,

Try to use grp) for local node group.


On Fri, Jul 8, 2016 at 9:48 AM, Kamal C <> wrote:

    I have a 3 node Ignite cluster and deployed a service using Node Singleton approach. The service started to run in all the 3 nodes.

Whenever a node stopped, the below line gets called as I'm doing resource cleanups inside IgniteService.cancel(ServiceContext context) method.


But, it cancels the service from all the nodes. How to cancel a locally running Ignite service gracefully?


Vladislav Pyatkov