Re: How do I know cache is fully replicated?

[Enes Akar]

Currently this is not supported in API.

You should shutdown instances one by one and track the migration logs (or management center). Migrations are logged by master node, so you should wait till migrations has been finished, at least you should be sure there is no immediate taks. There is log such "Remaining migration tasks in queue => Immediate-Tasks: 0"

On Sun, May 19, 2013 at 7:09 PM, <rickl...@gmail.com> wrote:

If using hazelcast for session replication (or any storage) and I anticipate intentional server rolling, how do I manage that?

Say I'm set up for one copy of each node. And server B is the backup of server C.

Then I have to restart servers (roll out new release). I take down A. Now I have to ensure A's data goes somewhere else in addition to B. Because if I take down A and B at the same time, I'll lose data correct?

Is there an api call to know the cache is 'stable', and it's ok to take down another node? A typical scenario would be rolling 3 servers at once out of 10.

--
You received this message because you are subscribed to the Google Groups "Hazelcast" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hazelcast+...@googlegroups.com.
To post to this group, send email to haze...@googlegroups.com.
Visit this group at http://groups.google.com/group/hazelcast?hl=en-US.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--

Enes Akar

Hazelcast | Open source in-memory data grid
Mobile: +90.505.394.1668