When we found that a mysql pod was isolated and was able to switch normally. But the network recovery will not automatically append to the slave instance.
Because there is no change in this pod when the network is restored, no update or create will be triggered and the status is normal. It will not allow the operator to automatically create the master mechanism.
This is the fix for that.
[ ] I've made sure the CHANGELOG.md will remain up-to-date after this PR is merged.
jiuker
commented
1 year ago
closes/fixes #xyz
When we found that a mysql pod was isolated and was able to switch normally. But the network recovery will not automatically append to the slave instance. Because there is no change in this pod when the network is restored, no update or create will be triggered and the status is normal. It will not allow the operator to automatically create the master mechanism. This is the fix for that.