Bug #90829 Drop PROCEDURE- different errors on master and slave.

• Submitted: 11 May 2018 4:18
• Modified: 22 May 2018 9:44
• Reporter: Nam Le
• Status: Not a Bug
• Category: MySQL Server
• Severity: S3 (Non-critical)
• Version: 5.7.20
• OS: CentOS
• CPU Architecture: Any

[11 May 2018 4:18] Nam Le

Description:
Description:
We are using master-master replication mysql server 5.7.20.
Run mysql query DROP PROCEDURE on master, after that slave has Error:

2018-05-10T06:12:37.333898Z 127 [ERROR] /usr/sbin/mysqld: Cannot load from mysql.procs_priv. The table is probably corrupted
2018-05-10T06:12:37.345212Z 127 [ERROR] Slave SQL for channel '': Error 'Cannot load from mysql.procs_priv. The table is probably corrupted' on query. Default database: 'X_DB'. Query: 'DROP PROCEDURE IF EXISTS procedure_name', Error_code: 1728

How to repeat:
How to repeat:
Test
1. master-master replication
2. run mysql query on master DROP PROCEDURE test;
3. check slave for Error: SHOW SLAVE STATUS\G

Suggested fix:
Suggested fix:
Workaround:
run that on defect slave server
1. STOP SLAVE;
2. SET GLOBAL sql_slave_skip_counter = 1; 
3. START SLAVE;

[22 May 2018 9:44] MySQL Verification Team

Thank you for taking the time to write to us, but this is not a bug. Please double-check the documentation available at https://dev.mysql.com/doc/refman/5.7/en/mysql-upgrade.html and the instructions on how to report a bug at http://bugs.mysql.com/how-to-report.php

Have you upgraded/downgraded problem-ed MySQL server(slave's in your case) but forget to run mysql_upgrade? If the mysql.proc is not in the format which server expects i.e column def different etc then you may see such messge.

Thanks,
Umesh