Bug #37454 | CREATE USER breaks replication on 5.0.37 when user already exists on slave | ||
---|---|---|---|
Submitted: | 17 Jun 2008 17:35 | Modified: | 17 Jun 2008 20:47 |
Reporter: | Mark Konetchy | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server: Replication | Severity: | S3 (Non-critical) |
Version: | 5.0.37, 5.0, 5.1, 6.0 BK | OS: | Linux |
Assigned to: | CPU Architecture: | Any | |
Tags: | create user, replication |
[17 Jun 2008 17:35]
Mark Konetchy
[17 Jun 2008 19:44]
Peter Laursen
I understand your post like this: "Replication [does not break when replicating] from 5.0.37 to 5.0.41" Well -- if this is fixed in 5.0.41 and onwards what else do you think could be done now? It is not possible to fix bug 'backwards' (in old releases) only 'forwards' (in new releases). Frankly I do not understand the idea of posting such report - or I do not understand the meaning of what you are writing! Am I missing something? Peter (not a MySQL person)
[17 Jun 2008 20:47]
Sveta Smirnova
Thank you for taking the time to write to us, but this is not a bug. Please double-check the documentation available at http://dev.mysql.com/doc/ and the instructions on how to report a bug at http://bugs.mysql.com/how-to-report.php GRANT statements are replicated, so if you have user on slave error is expected. Like in not replication setup: $mysql Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 296 Server version: 5.0.51a-log MySQL Community Server (GPL) Type 'help;' or '\h' for help. Type '\c' to clear the buffer. mysql> create user bar; Query OK, 0 rows affected (0.09 sec) mysql> create user bar; ERROR 1396 (HY000): Operation CREATE USER failed for 'bar'@'%'
[19 Mar 2014 13:01]
NOT_FOUND NOT_FOUND
Workaround: slave> stop slave; slave> reset slave; master> reset master; slave> drop user repl_test; slave> start slave;