On Thu, Mar 31, 2016 at 8:58 AM, dstieglitz <dstiegl...@stainlesscode.com> wrote:
> Hi folks: > > We're trying to deploy a clustered singleton service. In our Service > implementation object we have a reference to another object that is > initialized in the init() method. > > We've observed that upon topology change, this object can go "null." > This is normal, since the service state is not moved. All Ignite does is make sure that the service is immediately started on another node and calls “init()” again. > Is init() called again when the > service has to migrate to a new node? > Yes. > > Dan > > > > -- > View this message in context: > http://apache-ignite-users.70518.x6.nabble.com/Behavior-of-init-for-clustered-singleton-tp3819.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. >
