[BUG] In a MySQL Group Replication (MGR) cluster architecture, a primary node failure may lead to a split-brain scenario

[duanhui8]

Describe the bug 1.Use sysbench to stress-test the cluster, inducing data replication delays on the secondary nodes.

2.Manually shut down the primary node of the MGR cluster.

3.At this point, the MGR cluster will elect a new primary. Simultaneously, if the old primary node is restarted (e.g., by a syncer process), it may attempt to rejoin and trigger a split-brain scenario by also claiming itself as the primary (the previously failed node).

To Reproduce Steps to reproduce the behavior:

Expected behavior A clear and concise description of what you expected to happen.

Screenshots If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• kubeblocks beta41

Additional context Add any other context about the problem here.

[duanhui8]

[duanhui8]

kubeblocks v1.0 beta44

[github-actions[bot]]

This issue has been marked as stale because it has been open for 30 days with no activity

[xuriwuyun]

The problem is resolved. Please upgrade the syncer image to latest (0.5.0, no changes required) and try again.