Hi,
Thank's for the clarificaiton! That's what I expected.
I looked into https://github.com/luqmanahmad/ignite-plugins and decided to
implement my own SegmentationResolver to deal with these cases.
Cheers Sam
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hello!
After all, it is only you who can decide whether your cluster has segmented
or not. The traditional solution is "the largest one wins", but if the
parts of cluster can't communicate, it becomes undecidable.
Regards,
--
Ilya Kasnacheev
пн, 14 сент. 2020 г. в 12:01, sue :
> Hi Denis,
>
>
Hi Denis,
Thank you for your reply.
Restarting all the nodes in the partitioned segment would work for my
usecase.
Is there a way to detect such a scenario with TCP/IP Discovery mode in
Ignite?
In my test I didn't get any EVT_NODE_SEGMENTED events, only EVT_NODE_FAILED.
So the individual cluste
BTW, you can try zookeeper discovery, I think it's the easier way to
resolve split-brain problem:
https://www.gridgain.com/docs/latest/developers-guide/clustering/zookeeper-discovery
пт, 11 сент. 2020 г. в 14:13, Michael Cherkasov :
> Make sure first you stop all nodes in one segment and only th
Make sure first you stop all nodes in one segment and only then start them,
rolling restart might not fix cluster segmentation.
пт, 11 сент. 2020 г. в 09:08, Denis Magda :
> Hi Samuel,
>
> With the current behavior, the segments will not rejoin automatically.
> Once the network is recovered from
Hi Samuel,
With the current behavior, the segments will not rejoin automatically. Once
the network is recovered from a network partitioning event, you need to
restart all the nodes of one of the segments. Those nodes will join the
other nodes and the cluster will become fully operational.
Let me
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 expected it to
do.
F
