Thanks for providing the answers Val!
A. Actually, I forgot that Ignite service accepts predicate.
B. Two IgniteService are not running in a node. I meant two
Service object creation.
- Ignite auto-deploys the service
- Manual service deployment using java code.
In my test, IgniteService starts to process the request before it gets
initialized
which may leads to incorrect results. I've listed the steps to reproduce the
issue and exception thrown in a gist[1]
[1] https://gist.github.com/Kamal15/0f4175fdcfd2c4ef909150be5d896c56
Regards,
Kamal C
On Sat, Jul 30, 2016 at 5:31 AM, vkulichenko <[email protected]>
wrote:
> Hi Kamal,
>
> A. You can provide the cluster group with local node only:
>
> ignite.services(ignite.cluster().forLocal()).deploy(...);
>
> B. If you start the service with the same name, this should not happen. I
> tried to reproduce your behavior, but everything works as expected for me.
> Do you a have a test that you can share?
>
> -Val
>
>
>
> --
> View this message in context:
> http://apache-ignite-users.70518.x6.nabble.com/Ignite-Services-How-to-preserve-value-of-Local-variables-tp4094p6637.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>
