Bug #71005 | Documentation needs clarification on upgrading replication setups | ||
---|---|---|---|
Submitted: | 25 Nov 2013 21:35 | Modified: | 1 Mar 2022 22:26 |
Reporter: | James Lucas | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Documentation | Severity: | S3 (Non-critical) |
Version: | 5.5+ | OS: | Any |
Assigned to: | CPU Architecture: | Any | |
Tags: | documentation, mysql_upgrade, replication |
[25 Nov 2013 21:35]
James Lucas
[27 Nov 2013 8:46]
Jon Stephens
Replication -> mine.
[11 Dec 2013 21:55]
James Lucas
Just wanted to note that I opened an SR with Oracle Support, and was told the proper high level upgrade procedure in my situation would be <shutdown slave> <upgrade slave binaries> <startup slave> mysql_upgrade -u root -p --skip-write-binlog <on slave> <shutdown master> <upgrade master binaries> <startup master> mysql_upgrade -u root -p --skip-write-binlog <on master>
[1 Mar 2022 22:26]
Margaret Fisher
Posted by developer: I am going through documentation bugs that have been on the back burner for a while. Thank you for the suggestion and apologies for the delay! I have updated the replication upgrade topics to reorganize them and add the procedure here: https://dev.mysql.com/doc/refman/5.7/en/replication-upgrade.html https://dev.mysql.com/doc/refman/8.0/en/replication-upgrade.html Thanks for helping us improve the documentation!