Bug #76878 mysqlrplsync gives wrong information with server 5.7.7

• Submitted: 29 Apr 2015 8:43
• Modified: 12 Aug 2015 21:15
• Reporter: Peeyush Gupta
• Status: Closed
• Category: MySQL Utilities
• Severity: S3 (Non-critical)
• Version: 1.6.1
• OS: Any
• CPU Architecture: Any

[29 Apr 2015 8:43] Peeyush Gupta

Description:
With MySQL server 5.7.7 sys schema is included by default, so when mysqlrplsync checks
for data inconsistency between master and slaves, it compares checksums of sys schema tables
as well which differs and gives data inconsistency error.

How to repeat:
set up master slave replication and run mysqlrplsync utility 

python  ../scripts/mysqlrplsync.py --master=root:root@localhost:3310 --slaves=root:root@localhost:3311,root:root@localhost:3312
WARNING: Using a password on the command line interface can be insecure.
#
# GTID differences between Master and Slaves:
# - Slave 'localhost@3311' is up-to-date.
# - Slave 'localhost@3312' is up-to-date.
#
# Checking data consistency.
#
# Using Master 'localhost@3310' as base server for comparison.
# Checking 'sys' database...
# - Checking 'sys_config' table data...
#   [DIFF] `sys`.`sys_config` checksum for server 'localhost@3312'.
#   [DIFF] `sys`.`sys_config` checksum for server 'localhost@3311'.
#
#...done.
#
# SUMMARY: 2 data consistency issues found.
#

Suggested fix:
Skip comparing checksums of sys schema tables between master and slave fro MySQL server 5.7.7 and above

[12 Aug 2015 21:15] Philip Olson

Posted by developer:
 
Fixed as of the upcoming MySQL Utilities 1.5.5 / 1.6.2 releases, and here's the changelog entry:

The mysqlrplsync and mysqldbcompare utilities now function correctly when
the sys schema is present; a schema that is added by default as of MySQL
server 5.7.7. In other words, the sys table is no longer compared/synced
as it is unique to each host.

Thank you for the bug report.