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 know if you have any other questions or guidance with this.
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 <[hidden email]>:
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 <[hidden email]>:
In reply to this post by dmagda
Thank you for your reply.
Restarting all the nodes in the partitioned segment would work for my
Is there a way to detect such a scenario with TCP/IP Discovery mode in
In my test I didn't get any EVT_NODE_SEGMENTED events, only EVT_NODE_FAILED.
So the individual cluster nodes would not be able to distinguish between
failed nodes and network segmentation.
@Mikhail: Thank you for the tip with zookeeper, I'll check that out.
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
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.
пн, 14 сент. 2020 г. в 12:01, sue <[hidden email]>:
|Free forum by Nabble||Edit this page|