Reducing Risk Before Upgrading MySQL
summary
Process shows exact steps: provision a spare server, create a MySQL 5.7 replica of 5.6, run pt-table-checksum to find inconsistencies (example: a 44,000‑row chunk, 12 bad chunks), fix causes and repeat, run pt-upgrade on slow‑log samples to catch errors, warnings and a 70x regression (fixable by disabling index_merge_intersection or adding a composite index), validate full workload with query‑playback or ProxySQL mirroring, test rollback by replicating 56→57→56, then only cutover after checks are clean.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:36Oracle Documentation
- 3:32Oracle Recommendations
- 8:23Documentation
- 9:45Potential Risks
- 15:48Upgrade Method
- 17:17Test Replication Consistency
- 19:08Rollback
- 19:27Add another machine
- 19:43rollback scenario testing
- 22:27non GTI
- 23:21PTtable checksum
- 24:26GT ID
- 34:37Query Playback
- 36:34Proxy SQL
- 37:51Migration Plan
- 42:02Migration Plan Summary
- 46:20Questions
