ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From pgarg <pg...@gridgain.com>
Subject Re: Replicated Cache Initialization timeout
Date Sat, 09 May 2015 07:12:38 GMT
/commented by dmitriy setrakyan/

Good approach.

To make sure that your singleton does not restart from scratch, you can
create a cache in your singleton service and periodically store your service
state in that cache. This way, whenever a crash happens, your service will
be able to restart from the last saved state.

----- 
/This post is migrated from now discontinued Apache Ignite forum at 
http://apacheignite.readme.io/v1.0/discuss/



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Replicated-Cache-Initialization-timeout-tp127p131.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Mime
View raw message