You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Issues encountered during MySQL ORC mode testing:
The primary node frequently restarts, and the replica may encounter IO thread anomalies: "could not find next log; the first event '' at 4, the last event read from '/var/lib/mysql/binlog/example-mysql-cluster-mysql-0-bin.000002' at 197," while the primary node does not have the 000002 file.
After multiple master-slave switches, a multi-master situation may arise where they are synchronizing with each other.
The MasterFailoverLostInstancesDowntimeMinutes configuration marks nodes as being in a "downtimed" state for ten minutes after an anomaly occurs. However, if pods are deleted during this period, various abnormal conditions may occur.
The replica node is not detected by ORC, resulting in failures in executing failover and switchover operations.
The text was updated successfully, but these errors were encountered:
Describe the bug
Issues encountered during MySQL ORC mode testing:
The primary node frequently restarts, and the replica may encounter IO thread anomalies: "could not find next log; the first event '' at 4, the last event read from '/var/lib/mysql/binlog/example-mysql-cluster-mysql-0-bin.000002' at 197," while the primary node does not have the 000002 file.
After multiple master-slave switches, a multi-master situation may arise where they are synchronizing with each other.
The MasterFailoverLostInstancesDowntimeMinutes configuration marks nodes as being in a "downtimed" state for ten minutes after an anomaly occurs. However, if pods are deleted during this period, various abnormal conditions may occur.
The replica node is not detected by ORC, resulting in failures in executing failover and switchover operations.
The text was updated successfully, but these errors were encountered: