Re: Replica won't connect to Master after server restart
Thanks Peter for your input, it's highly appreciated.
To answer all your questions.
Yes, The replica is indeed reaching and connecting to the master... I don't know why this error came to be in the first place, but you're also right on your assupmtion as the replica server was restarted after a Windows Update installation.
Well, the replica was fully replicated before I stopped it to perform the windows update, but when it came only, it wouldn't sync with the master any more, all binary logs are still in the master by the way.
I think it's also important to note the MySQL version I'm running and the O.S. on top of it.
MySQL 8.0.29 on both master and replica, Windows 2019 Standard
*************************** 1. row ***************************
Replica_IO_State: Waiting for source to send event
Source_Host: 192.168.2.165
Source_User: replica_user
Source_Port: 3306
Connect_Retry: 60
Source_Log_File: LD-PROP-bin.000015
Read_Source_Log_Pos: 380705379
Relay_Log_File: NY-Prop-relay-bin.000027
Relay_Log_Pos: 206798
Relay_Source_Log_File: LD-PROP-bin.000008
Replica_IO_Running: Yes
Replica_SQL_Running: No
Replicate_Do_DB:
Replicate_Ignore_DB:
Replicate_Do_Table:
Replicate_Ignore_Table:
Replicate_Wild_Do_Table:
Replicate_Wild_Ignore_Table:
Last_Errno: 1062
Last_Error: Coordinator stopped because there were error(s) in the worker(s). The most recent failure being: Worker 1 failed executing transaction 'ANONYMOUS' at master log LD-PROP-bin.000008, end_log_pos 138018018. See error log and/or performance_schema.replication_applier_status_by_worker table for more details about this failure or others, if any.
Skip_Counter: 0
Exec_Source_Log_Pos: 138017521
Relay_Log_Space: 7759382624
Until_Condition: None
Until_Log_File:
Until_Log_Pos: 0
Source_SSL_Allowed: No
Source_SSL_CA_File:
Source_SSL_CA_Path:
Source_SSL_Cert:
Source_SSL_Cipher:
Source_SSL_Key:
Seconds_Behind_Source: NULL
Source_SSL_Verify_Server_Cert: No
Last_IO_Errno: 0
Last_IO_Error:
Last_SQL_Errno: 1062
Last_SQL_Error: Coordinator stopped because there were error(s) in the worker(s). The most recent failure being: Worker 1 failed executing transaction 'ANONYMOUS' at master log LD-PROP-bin.000008, end_log_pos 138018018. See error log and/or performance_schema.replication_applier_status_by_worker table for more details about this failure or others, if any.
Replicate_Ignore_Server_Ids:
Source_Server_Id: 1
Source_UUID: e60ea3eb-db45-11ec-ae0e-005056bad68e
Source_Info_File: mysql.slave_master_info
SQL_Delay: 0
SQL_Remaining_Delay: NULL
Replica_SQL_Running_State:
Source_Retry_Count: 86400
Source_Bind:
Last_IO_Error_Timestamp:
Last_SQL_Error_Timestamp: 220719 13:42:46
Source_SSL_Crl:
Source_SSL_Crlpath:
Retrieved_Gtid_Set:
Executed_Gtid_Set:
Auto_Position: 0
Replicate_Rewrite_DB:
Channel_Name:
Source_TLS_Version:
Source_public_key_path:
Get_Source_public_key: 0
Network_Namespace:
1 row in set (0.02 sec)
ERROR:
No query specified
Subject
Views
Written By
Posted
2053
July 19, 2022 07:24AM
604
July 19, 2022 03:37PM
Re: Replica won't connect to Master after server restart
999
July 20, 2022 06:45AM
558
July 20, 2022 12:19PM
509
July 20, 2022 12:35PM
564
July 20, 2022 01:16PM
490
July 22, 2022 05:40AM
466
July 22, 2022 07:01AM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.