| Bug #50862 | mysql_upgrade breaks replication | ||
|---|---|---|---|
| Submitted: | 2 Feb 2010 21:57 | Modified: | 3 Feb 2010 6:53 |
| Reporter: | Michael McLagan | Email Updates: | |
| Status: | Duplicate | Impact on me: | |
| Category: | MySQL Server: Replication | Severity: | S2 (Serious) |
| Version: | 5.1.43 | OS: | Linux |
| Assigned to: | CPU Architecture: | Any | |
[3 Feb 2010 6:25]
MySQL Verification Team
are you saying --skip-write-binlog option of mysql_upgrade should be enabled by default so changes won't be sent to the slaves ?
[3 Feb 2010 6:53]
Sveta Smirnova
Please do not submit the same bug more than once. An existing bug report already describes this very problem. Even if you feel that your issue is somewhat different, the resolution is likely to be the same. Because of this, we hope you add your comments to the original bug instead. Thank you for your interest in MySQL. Duplicate of bug #46638
Description: Executing mysql_upgrade on master causes slaves to fail with the following error: Last_Errno: 1580 Last_Error: Error 'You cannot 'ALTER' a log table if logging is enabled' on query. Default database: 'mysql'. Query: 'ALTER TABLE slow_log MODIFY COLUMN server_id INTEGER UNSIGNED NOT NULL' Skipping the command restarts replication. How to repeat: Set up replication, master and slave. Turn on slow logging on both. Execute mysql_upgrade on both master and slave.