Bug #37279 Dropped table with events can prevent node restart
Submitted: 9 Jun 2008 11:41 Modified: 2 Jul 2008 15:11
Reporter: Jonas Oreland Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version: OS:Any
Assigned to: Jonas Oreland CPU Architecture:Any

[9 Jun 2008 11:41] Jonas Oreland 
Description:
1) create table (using mysqld)
2) start ndbapi program listening on events from table
3) drop table (using mysqld)
4) restart node (initial or normal)

How to repeat:
see above

Suggested fix:
dont copy dropped subscriptions
[11 Jun 2008 10:11] Jonas Oreland 
patch pushed...somehow got missed
[11 Jun 2008 15:26] 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/47741

2620 jonas@mysql.com	2008-06-11
      ndb - bug#37279
              Dont copy dropped subscriptions during node restart
              cause it will cause starting node to crash
[16 Jun 2008 6:25] 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/47885

2623 jonas@mysql.com	2008-06-16
      ndb - bug#37279
        patch 2, copy dropped subsriptions
        or starting suma will be confused
[2 Jul 2008 6:58] Jonas Oreland 
pushed into 6.3.16 and 6.2.16
[2 Jul 2008 15:11] Jon Stephens 
Documented in the NDB 6.2.16 and 6.3.16 changelogs as follows:

        Creating a table on an SQL node, then starting an NDB API application that
        listened for events from this table, then dropping the table from an SQL 
        node, prevented data node restarts.
[12 Dec 2008 23:30] Bugs System 
Pushed into 6.0.6-alpha  (revid:jonas@mysql.com-20080616062529-48f0q1etvbuqyz1x) (version source revid:jonas@mysql.com-20080812185642-1nevjb94zj621dqx) (pib:5)