Grid state check before it's completely caught up

classic Classic list List threaded Threaded
3 messages Options
Anirudha Jadhav Anirudha Jadhav
Reply | Threaded
Open this post in threaded view
|

Grid state check before it's completely caught up

Ignite 2.5 

Is there a way to ensure grid nodes don't serve any requests until they are caught up with the replicated state in the cluster?

Thanks 
--
Anirudha P. Jadhav
dkarachentsev dkarachentsev
Reply | Threaded
Open this post in threaded view
|

Re: Grid state check before it's completely caught up

Hi,

You can, for example, set SYNC rebalance mode for your replicated cache [1].
In that case all cache operations will be blocked unless rebalance is
finished, and when it's done you'll get a fully replicated cache.
But this will block cache on each topology change.

[1]
https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/configuration/CacheConfiguration.html#setRebalanceMode-org.apache.ignite.cache.CacheRebalanceMode-

Thanks!
-Dmitry



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Anirudha Jadhav Anirudha Jadhav
Reply | Threaded
Open this post in threaded view
|

Re: Grid state check before it's completely caught up

thanks!

On Fri, Aug 31, 2018 at 12:28 PM dkarachentsev <[hidden email]> wrote:
Hi,

You can, for example, set SYNC rebalance mode for your replicated cache [1].
In that case all cache operations will be blocked unless rebalance is
finished, and when it's done you'll get a fully replicated cache.
But this will block cache on each topology change.

[1]
https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/configuration/CacheConfiguration.html#setRebalanceMode-org.apache.ignite.cache.CacheRebalanceMode-

Thanks!
-Dmitry



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/


--
Anirudha P. Jadhav