Hi Kamal, This issue is related to this one: https://issues.apache.org/jira/browse/IGNITE-3392. Current service deployment process is asynchronous, so if it takes a lot of time to deploy it, you can get these exceptions in the logs. Note that they actually do not break anything, everything becomes stable after the service is executed on the second node.
Consider using Compute Grid [1] instead. It can a better option if you use only node singletons and if they don't have any specific lifecycle. I.e., if they are used to execute a piece of code on a server node. [1] https://apacheignite.readme.io/docs/compute-grid -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-Services-How-to-preserve-value-of-Local-variables-tp4094p6686.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
