Bug #81206 | Not possible to upgrade GTID servers safely to MySQL 5.7 | ||
---|---|---|---|
Submitted: | 27 Apr 2016 4:59 | Modified: | 16 Jan 2018 13:08 |
Reporter: | monty solomon | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Documentation | Severity: | S3 (Non-critical) |
Version: | 5.7.11 | OS: | CentOS |
Assigned to: | CPU Architecture: | Any |
[27 Apr 2016 4:59]
monty solomon
[8 Aug 2017 18:54]
MySQL Verification Team
Hi, Yes, documentation could be bit clearer about upgrade procedure when using GTID, and especially if, by whatever reason, you still have some myisam tables. thanks Bogdan
[16 Jan 2018 13:08]
Margaret Fisher
Posted by developer: I believe we have now resolved this under the docs changes for BugĀ #27199182. The restriction in https://dev.mysql.com/doc/refman/5.7/en/upgrading.html has been replaced by the warning about loading a dump file including system tables when GTIDs are enabled. The restriction in https://dev.mysql.com/doc/refman/5.7/en/replication-gtids-restrictions.html has been changed to: GTID mode and mysql_upgrade. When the server is running with global transaction identifiers (GTIDs) enabled (gtid_mode=ON), do not enable binary logging by mysql_upgrade (the --write-binlog option). Thanks again for your report.