Need method to upgrade safely when using GTID

Bug #1575480 reported by monty solomon
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MySQL Server
Unknown
Unknown
Percona Server moved to https://jira.percona.com/projects/PS
Won't Fix
Undecided
Unassigned

Bug Description

There are neither instructions nor guidance provided how to upgrade from MySQL 5.6 to MySQL 5.7 when using GTID.

It is necessary to run mysql_upgrade as part of the upgrade to MySQL 5.7 from MySQL 5.6 but it is not possible to turn off GTID on MySQL 5.6 without shutting down the complete cluster and the documentation states that mysql_upgrade should not be used with GTID.

How to repeat:
The documentation states

https://dev.mysql.com/doc/refman/5.7/en/upgrading.html

Note
mysql_upgrade should not be used when the server is running with --gtid-mode=ON. See GTID mode and mysql_upgrade for more information.

and states

https://dev.mysql.com/doc/refman/5.7/en/replication-gtids-restrictions.html

GTID mode and mysql_upgrade. It is possible but is not recommended to use mysql_upgrade on a MySQL Server running with --gtid-mode=ON, since mysql_upgrade can make changes to system tables that use the MyISAM storage engine, which is nontransactional.

Tags: doc upstream
Revision history for this message
monty solomon (monty+launchpad) wrote :
tags: added: upstream
Revision history for this message
Laurynas Biveinis (laurynas-biveinis) wrote :

Upstream has verified this as a documentation bug. This is best fixed there.

Changed in percona-server:
status: New → Won't Fix
tags: added: doc
Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

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

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.