Replication breaks on some gateway after installing patch Layer7_API_PlatformUpdate_64bit_v11.0-Debian-2024-09-24.L7P
search cancel

Replication breaks on some gateway after installing patch Layer7_API_PlatformUpdate_64bit_v11.0-Debian-2024-09-24.L7P

book

Article ID: 385109

calendar_today

Updated On:

Products

CA API Gateway

Issue/Introduction

Please may I know if there are any known errors when installing the patch on API GATEWAY


Our replication broke the moment we installed the first patch with the following error

2024-11-19T10:13:02.524438Z 442827 [ERROR] [MY-010584] [Repl] Replica I/O for channel '': Error reconnecting to source '<serverName>'. This was attempt 1/86400, with a delay of 100 seconds between attempts. Message: Can't connect to MySQL server on '<serverName>' (111), Error_code: MY-002003
2024-11-19T10:13:02.521746Z 442827 [Warning] [MY-010897] [Repl] Storing MySQL user name

Cause

Mysql on primary was shutdown by user multiple times , similarly on the secondary node . which might have impacted the replication .

From gateway side many outside factors that can result in needing to rebuild DB - first 2 are the usual suspects

Relay Log corruption
Long slave connection timeout 
Long running update statements causing slave to lag
Data drift
Bad server_id values  
Master not writing binlog
Replicate_ignore/do_db rules
RESET MASTER / RESET SLAVE
Manually deleting binlogs or relay logs
Purging master logs
Bad CHANGE MASTER TO statement.

Resolution

In this type of scenario I would like you to reinitialize the replication properly. For re-initialization kindly follow the below article.

https://knowledge.broadcom.com/external/article?articleNumber=44402

 

Additional Information

https://knowledge.broadcom.com/external/article?articleNumber=44402