T15:17:04.126291Z 0 Plugin group_replication reported: 'Group membership changed: This member has left the group.' T15:17:01.048160Z 0 Plugin group_replication reported: 'Message received while the plugin is not ready, message discarded.' T15:17:01.048055Z 0 Plugin group_replication reported: 'There was a previous plugin error while the member joined the group. Fix the problem, and restart the slave SQL thread with "SLAVE START". T15:16:59.820955Z 4677 Error running query, slave SQL thread aborted. T15:16:59.820834Z 4675 Plugin group_replication reported: 'The server was automatically set into read only mode after an error was detected.' Check performance_schema.replication_group_members to check group membership information.' T15:16:59.820820Z 4675 Plugin group_replication reported: 'Unable to confirm whether the server has left the group or not. T15:16:59.820797Z 4675 Plugin group_replication reported: ' The member is leaving a group without being on one.' T15:16:59.820741Z 4675 Plugin group_replication reported: 'Fatal error during execution on the Applier process of Group Replication. Unable to process more transactions, this member will now leave the group.' T15:16:59.820703Z 4677 Plugin group_replication reported: 'The applier thread execution was aborted. If you want to check the master's binary log or slave's relay log, you will be able to know their names by issuing 'SHOW SLAVE STATUS' on this slave. The possible reasons are: the master's binary log is corrupted (you can check this by running 'mysqlbinlog' on the binary log), the slave's relay log is corrupted (you can check this by running 'mysqlbinlog' on the relay log), a network problem, the server was unable to fetch a keyring key required to open an encrypted relay log file, or a bug in the master's or slave's MySQL code. T15:16:59.820680Z 4677 Slave SQL for channel 'group_replication_applier': Relay log read failure: Could not parse relay log event entry. T15:16:59.820634Z 4677 Error reading relay log event for channel 'group_replication_applier': corrupted data in log event New state master_host='', master_port= 0, master_log_file='', master_log_pos= 4, master_bind=''. Previous state master_host='', master_port= 0, master_log_file='', master_log_pos= 4, master_bind=''.
T15:16:59.804045Z 4675 'CHANGE MASTER TO FOR CHANNEL 'group_replication_applier' executed'.
T15:16:59.775753Z 4670 Plugin group_replication reported: ' Automatically adding IPv6 localhost address to the allowlist. T15:16:59.775731Z 4670 Plugin group_replication reported: ' Automatically adding IPv4 localhost address to the allowlist.
T15:16:59.774179Z 4670 Plugin group_replication reported: 'Plugin 'group_replication' is starting.' T15:10:38.532436Z 2 Plugin group_replication reported: ' The member is already leaving or joining a group.' T15:10:38.532322Z 2 Plugin group_replication reported: 'Timeout on wait for view after joining group' T15:10:34.970383Z 0 Plugin group_replication reported: ' The member was unable to join the group. T15:10:34.915451Z 0 Plugin group_replication reported: ' Error connecting to all peers. var/log/mysql/error.log T15:10:34.915404Z 0 Plugin group_replication reported: ' Error on opening a connection to peer node 172.16.58.101:33061 when joining a group. No we have one unit in an error state with hook failed: "cluster-relation-departed"Īnd one in the block state with Cluster is inaccessible from this instance. We also tried adding a new unit and adding this unit to the pre existing cluster, but this did not work And we are really frustrated now… It would be extremely awesome if we could get some help. Our mysql innodbcluster seems totally broken, we only have one active unit which is okay in terms that we can still use our openstack deployment even tho it has no failover, we tried rejoining, add-instances and first of all we tried the reboot-cluster-from-complete outage action, but we cant get all three to work, in out testing environment we had no problems at all.
0 kommentar(er)
