MySQL Replication Slave I/O error upon API Gateway restart on MySql8 and Gateway 10
search cancel

MySQL Replication Slave I/O error upon API Gateway restart on MySql8 and Gateway 10

book

Article ID: 195804

calendar_today

Updated On: 07-20-2022

Products

CA API Gateway API SECURITY CA API Gateway Precision API Monitoring Module for API Gateway (Layer 7) CA API Gateway Enterprise Service Manager (Layer 7) STARTER PACK-7 CA Microgateway

Issue/Introduction



If restart mysql on one node after setting up replication, the following error occurs.

==============================================================

[System] [MY-010562] [Repl] Slave I/O thread for channel '': connected to master 'repluser@xxx:3306',replication started in log 'ssgbin-log.000263' at position 195
[ERROR] [MY-010557] [Repl] Error reading packet from server for channel '': Lost connection to MySQL server during query (server_errno=2013)

The 2 mysql nodes keep restarting themselves by turn.

Environment

Release : 10.0

Component : API GATEWAY

Cause

Should be due to mysql bug #30774692: MYSQL CRASHES WITH SLAVE_COMPRESSED_PROTOCOL=ON

Resolution

Workaround:

Before the new patch or version to release, the following workaround will fix the issue,

  1.  change the following line in /opt/SecureSpan/Appliance/create_slave.sh
    MASTER_COMPRESSION_ALGORITHMS='zlib,uncompressed', 
    to 
    MASTER_COMPRESSION_ALGORITHMS='uncompressed',
  2. use the new create_slave.sh to rebuild the replication (on both nodes)

 

Solution:

Upgrade the mysql to 8.0.20 or above -- applying the latest platform patch will upgrade the mysql and fix the issue.

Additional Information

https://github.com/mysql/mysql-server/commit/3bb12a7a564265c5f149c887253af903ebbf77a9

 

https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/release-announcements/CA-API-Gateway-Solutions--Patches/3024