Bug #30877 Trailing event cannot be removed, hence replication cannot be set up
Submitted: 6 Sep 2007 19:55 Modified: 7 Jan 2008 11:28
Reporter: Tomas Ulin Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:5.1 OS:Any
Assigned to: Tomas Ulin CPU Architecture:Any

[6 Sep 2007 19:55] Tomas Ulin 
Description:
when for some reason an ndb event is left behind and the table is later recreated and it gets a different tableid, the event cannot be dropped

How to repeat:
.
[6 Sep 2007 19:57] Bugs System 
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/33862

ChangeSet@1.2604, 2007-09-06 22:05:46+02:00, tomas@whalegate.ndb.mysql.com +6 -0
  Bug #30877  	cluster: trailing event cannot be removed, and hence replication cannot be setup
[20 Sep 2007 14:22] Jon Stephens 
Documented in mysql-5.1.22-ndb-6.2.6 and mysql-5.1.22-ndb-6.3.2 changelogs, left in PP status for 5.1-main push.
[7 Jan 2008 11:28] Jon Stephens 
Closed w/o further action per comment from Tomas.
[7 Jan 2008 11:29] Jon Stephens 
Closed w/o further action per comment from Tomas.