I've been testing Ignite (2.8.1) and it's behaviour under network
> segmentation.
> According to the docs, Ignite nodes should be able to detect network
> segmentation and apply the configured SegmentationPolicy.
>
> However the segmentation handling didn't trigger
Hi
I've been testing Ignite (2.8.1) and it's behaviour under network
segmentation.
According to the docs, Ignite nodes should be able to detect network
segmentation and apply the configured SegmentationPolicy.
However the segmentation handling didn't trigger as I would have ex
Hi Luqman,
Does your plugin just detect a segmentation occurrence? Or does it also
resolve the split-brain condition?
Thanks,
Jose
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi Jose,
It is backward compatible.
Instructions for building with different version of ignite are already on
https://github.com/luqmanahmad/ignite-plugins#usage.
Let me know if you need any help with it.
Thanks,
Luqman
On Thu, Dec 6, 2018 at 5:59 AM joseheitor wrote:
> Hi Luqman,
>
> Is you
Hi Luqman,
Is your Segmentation plugin compatible with Ignite version 2.7.0...?
Thanks,
Jose
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
What does it provide on top of the Zookeeper split brain resolver?
https://apacheignite.readme.io/docs/zookeeper-discovery
On Fri, Sep 14, 2018 at 3:59 AM Kopilov wrote:
> luqmanahmad, what does this plugin definitely do?
> Can it help to avoid segmentation or only to detect them?
> Can it be us
luqmanahmad, what does this plugin definitely do?
Can it help to avoid segmentation or only to detect them?
Can it be useful for my current problem:
http://apache-ignite-users.70518.x6.nabble.com/Unreasonable-segmentation-in-Kubernetes-on-one-node-reboot-tp24102.html
?
--
Sent from: http://apach
See [1] for free network segmentation plugin
[1] https://github.com/luqmanahmad/ignite-plugins
<https://github.com/luqmanahmad/ignite-plugins>
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
See [1] for free network segmentation plugin
[1] https://github.com/luqmanahmad/ignite-plugins
<https://github.com/luqmanahmad/ignite-plugins>
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
See [1] for free network segmentation plugin
[1] https://github.com/luqmanahmad/ignite-plugins
<https://github.com/luqmanahmad/ignite-plugins>
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
encountering with split brain problem.
> To
> overcome that problem I have recently developed the plugin for network
> segmentation which can be downloaded from [1].
>
> This can be taken as a gift as it was a much needed functionality which was
> missing from the open source v
Thanks Dmitry. I have also added the initial version of TcpIpSegmentation -
Still not sure about it but hopefully it should fill the purpose - So far I
have tested it with postgres, sql server and tomcat
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi,
Nice work, thank you! I'm sure it will be very useful. Looking forward for
your contributions in Apache Ignite project ;)
Thanks!
-Dmitry
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi all,
Recently I was working on a project which required a very large number of
cluster over 700 nodes and we were encountering with split brain problem. To
overcome that problem I have recently developed the plugin for network
segmentation which can be downloaded from [1].
This can be taken
e.com/Network-Segmentation-tp14712p15020.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
605>
Thanks,
Luqman
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Network-Segmentation-tp14712p14714.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
We are running Ignite 1.7 on 20+ servers and using as distributed cache
store.
Caches are partitioned without backup (cacheMode=PARTITIONED, backups=0).
>From time to time we are getting network segmentation, so servers are
getting stopped as per default segmentation policy.
In our case we wo
ther nodes) the node.
On Thu, Oct 13, 2016 at 12:40 PM, Yitzhak Molko
wrote:
> While I didn't configure any network segmentation properties
> (SegmentationResolvers, SegmentationResolveAttempts,
> SegmentCheckFrequency etc.) node is been shutdown from time to time:
> WARN : [discover
While I didn't configure any network segmentation properties
(SegmentationResolvers, SegmentationResolveAttempts, SegmentCheckFrequency
etc.) node is been shutdown from time to time:
WARN : [discovery.tcp.TcpDiscoverySpi] Date=2016/10/13/07/42/52/009|Node is
out of topology (probably, due to
Okay, that's how I supposed
Thank you all for your answers
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/network-segmentation-tp1772p1803.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
On Fri, Oct 30, 2015 at 12:14PM, Dmitriy Setrakyan wrote:
> Hi Agustin,
>
> I think the network segmentation API was ported to Apache Ignite by mistake
> when GridGain was donating its code to the Apache Ignite project in
> November, 2014.
>
> Currently the network segmenta
Hi Agustin,
I think the network segmentation API was ported to Apache Ignite by mistake
when GridGain was donating its code to the Apache Ignite project in
November, 2014.
Currently the network segmentation functionality is not implemented in
Apache Ignite, and is only available in the GridGain
imitation, or is only available in
enterprise edition?
Thank you.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/network-segmentation-tp1772p1776.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Hi Agustin,
Please provide the logs. It will help as to pin point the place that did
checks and always returned 'true'.
Regards,
Denis
On 10/30/2015 11:40 AM, Agustín Miña Blanco wrote:
Hi,
I have implemented a custom SegmentationResolver and I have added it
as a property of the IgniteConf
Hi,
I have implemented a custom SegmentationResolver and I have added it as a
property of the IgniteConfiguration.
In the logs I see that a new thread starts that is doing some segmentation
checking but my implementation is never called, instead the checking always
returns true.
Is this feature
25 matches
Mail list logo