You are viewing a plain text version of this content. The canonical link for it is here.

Posted to user@ignite.apache.org by Anirudha Jadhav <an...@nyu.edu> on 2018/08/30 05:14:35 UTC

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

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

Posted by Anirudha Jadhav <an...@nyu.edu>.

thanks!

On Fri, Aug 31, 2018 at 12:28 PM dkarachentsev <dk...@gridgain.com>
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

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

Posted by dkarachentsev <dk...@gridgain.com>.

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/