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 Mon, 26 Dec 2016 09:34:23 GMT
Hi Val,

Having two independently running clusters is fine with running ignite cache
in each cluster.

But I see cache is stopped because of network segmentation.



*Following the response to one of the query [1] -*

*Call chain:*


*org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.DiscoveryWorker#onSegmentation*
*org.apache.ignite.internal.managers.discovery.GridDiscoveryManager#stopNode*

*org.apache.ignite.Ignition#stop(java.lang.String, boolean)*

*You could change IgniteConfiguration.setSegmentationPolicy()
to SegmentationPolicy.NOOP, so the node will not be stopped upon
segmentation (the default value is STOP).*


I would feel NOOP as default network segmentation policy is better option
than STOP. Network segmentation is just temporary problem and independent
clusters can join as one cluster once is network is good. So STOP not makes
sense in this case.

What do you say ? thanks

1. http://apache-ignite-users.70518.x6.nabble.com/Cache-stopped-td9503.html


Thanks.

On 23 December 2016 at 00:29, vkulichenko <valentin.kulichenko@gmail.com>
wrote:

> Anil,
>
> Nothing is stopped. Once again, in case of segmentation you will have two
> independently running clusters. And in of the previous messages you told
> that this is desirable behavior for you as you have a read-only use case.
> Am
> I missing something? Did you run any test that gave different results?
>
> -Val
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/Ignite-cluster-tp9527p9707.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>

Mime
View raw message