gaqfl.blogg.se

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.