In-place upgrade upgrade creates replication discrepancies

[monty solomon]

After upgrading the slave and then the master from version 5.6 to 5.7 using the in-place upgrade there are replication discrepancies that were not present before the upgrade.

How to repeat:
Create new master and slave running MySQL 5.6.

Upgrade the slave to 5.7 using the in-place upgrade.

Upgrade the master to 5.7 using the in-place upgrade.

Compare the master and slave and observe multiple discrepancies.

[monty solomon (monty+launchpad)]

The timestamps for the columns in various tables are modified when mysql_upgrade is run and it is run separately on the slave(s) and then the master.

[monty solomon (monty+launchpad)]

I experienced this issue upgrading from 5.6 to 5.7. It may happen when upgrading from 5.5 to 5.6.

[monty solomon (monty+launchpad)]

I created upstream https://bugs.mysql.com/bug.php?id=81205

More details are available there.

[Muhammad Irfan (muhammad-irfan)]

I'm unable to replicate this problem on Percona Server 5.7.19 setup.

1) Setup Percona Server 5.6 master/slave.
2) In-place upgrade to Percona Server 5.7 for master/slave.

No replication discrepancies found.

[root@master ~]# pt-table-checksum --no-check-binlog-format --function murmur_hash --user checksum_user --password checksum_password --host master-ip --recursion-method=dsn=D=percona,t=dsns

# A software update is available:
            TS ERRORS DIFFS ROWS CHUNKS SKIPPED TIME TABLE
11-17T16:37:16 0 0 0 1 0 0.015 mysql.columns_priv
11-17T16:37:16 0 0 6 1 0 0.017 mysql.db
11-17T16:37:16 0 0 2 1 0 0.013 mysql.engine_cost
11-17T16:37:16 0 0 0 1 0 0.013 mysql.event
11-17T16:37:16 0 0 0 1 0 0.011 mysql.func
11-17T16:37:17 0 0 40 1 0 0.024 mysql.help_category
11-17T16:37:17 0 0 615 1 0 0.012 mysql.help_keyword
11-17T16:37:17 0 0 1253 1 0 0.012 mysql.help_relation
11-17T16:37:17 0 0 585 1 0 0.015 mysql.help_topic
11-17T16:37:17 0 0 0 1 0 0.009 mysql.ndb_binlog_index
11-17T16:37:17 0 0 0 1 0 0.010 mysql.plugin
11-17T16:37:17 0 0 48 1 0 0.014 mysql.proc
11-17T16:37:17 0 0 0 1 0 0.011 mysql.procs_priv
11-17T16:37:17 0 0 2 1 0 0.010 mysql.proxies_priv
11-17T16:37:17 0 0 6 1 0 0.010 mysql.server_cost
11-17T16:37:17 0 0 0 1 0 0.011 mysql.servers
11-17T16:37:17 0 0 2 1 0 0.010 mysql.tables_priv
11-17T16:37:17 0 0 0 1 0 0.010 mysql.time_zone
11-17T16:37:17 0 0 0 1 0 0.010 mysql.time_zone_leap_second
11-17T16:37:17 0 0 0 1 0 0.012 mysql.time_zone_name
11-17T16:37:17 0 0 0 1 0 0.010 mysql.time_zone_transition
11-17T16:37:17 0 0 0 1 0 0.010 mysql.time_zone_transition_type
11-17T16:37:17 0 0 9 1 0 0.011 mysql.user
11-17T16:37:17 0 0 1 1 0 0.008 percona.dsns
11-17T16:37:17 0 0 6 1 0 0.012 sys.sys_config
11-17T16:37:17 0 0 5 1 0 0.008 test.test

[Shahriyar Rzayev (rzayev-sehriyar)]

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3420