Bug #20384 Events: Event effects occur twice on slave
Submitted: 11 Jun 2006 23:17 Modified: 6 May 2007 3:10
Reporter: Lars Thalmann Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Replication Severity:S3 (Non-critical)
Version:5.1 OS:Any (All)
Assigned to: Chuck Bell CPU Architecture:Any

[11 Jun 2006 23:17] Lars Thalmann 
Description:
CREATE EVENT should be blocked on slave.

If it is not, then the effects of the event will be replicated *and* 
executed on slave causing double executing.

How to repeat:
Code review.

See also BUG#16421 and BUG#16425.
[3 Jan 2007 14:57] Lars Thalmann 
Patch marked WL#3629.
[19 Feb 2007 10:19] Rafal Somla 
Approved patch for WL#3629
[29 Mar 2007 15:27] Chuck Bell 
Patch for this bug included in WL#3629. Patch pushed 29 Mar 2007.
[31 Mar 2007 23:55] Bugs System 
Pushed into 5.1.18-beta
[6 May 2007 3:10] Jon Stephens 
Thank you for your bug report. This issue has been committed to our source repository of that product and will be incorporated into the next release.

If necessary, you can access the source repository and build the latest available version, including the bug fix. More information about accessing the source trees is available at

    http://dev.mysql.com/doc/en/installing-source.html

Documented fix in 5.1.18 changelog. Documented associated feature changes in Events, INFORMATION_SCHEMA, and Replication chapters of 5.1 Manual.

Updated synopsis, since the solution wasn't to disable CREATE EVENT itself, but rather make sure that the event was created but not executed on slave.