ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Anil <anilk...@gmail.com>
Subject Re: Ignite cluster
Date Wed, 21 Dec 2016 06:36:58 GMT
Thanks Val.

But the default STOP option not looks correct. There is always chance of
rejoining of cluster.
But if ignite cache is stopped because of segmentation, rejoin has no

Creating different clusters still fine as long as cache is not stopped in
case of network segmentation.

is there way to change the default value without setting network
segmentation policy?


On 20 December 2016 at 23:11, vkulichenko <valentin.kulichenko@gmail.com>

> Ignite doesn't have full segmentation resolution support out of the box.
> With
> Ignite you will always end up with two independent working cluster in case
> of segmentation. You will then have to restart on of these clusters, but if
> there were updates on the restarted cluster after the segmentation, they
> will be lost. The link provided above is for GridGain which has additional
> enterprise feature that allows to stop or restart on of the clusters
> automatically right after the segmentation, so there is no time frame with
> two cluster and you never lose updates.
> -Val
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/Ignite-cluster-tp9527p9649.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.

View raw message