A. How to deploy a service only in the local node?
Like, *Ignition.ignite().services().deploy(name, service);* (No
fault-tolerant)
B. In NodeSingleton approach, I expect only one instance of service should
be instantiated
in a node. In the below scenario:
- Node 1 calls IgniteService#deployNodeSingleton(name, serviceX) to deploy
the
service X in the grid
- Node 2 joins the cluster, Ignite automatially instantiates and deploys
the service X
on this node. This node also calls IgniteService#deployNodeSingleton(name,
serviceX)
since it don't know whether the service is deployed or not.
Two instances of ServiceX is created in Node 2. How to overcome that?
Regards,
Kamal C
On Wed, Apr 13, 2016 at 9:40 AM, vkulichenko <[email protected]>
wrote:
> This is already fixed in master. You can build from there and try it out,
> should work without implementation classes in the client.
>
> -Val
>
>
>
> --
> View this message in context:
> http://apache-ignite-users.70518.x6.nabble.com/Ignite-Services-How-to-preserve-value-of-Local-variables-tp4094p4112.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>
