MySQL Bugs: #38007: mysql.ndb_apply_status should not be deleted

Bug #38007	mysql.ndb_apply_status should not be deleted
Submitted:	10 Jul 2008 6:04	Modified:	28 Feb 2010 16:18
Reporter:	Mikiya Okuno	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S3 (Non-critical)
Version:	mysql-5.1	OS:	Any
Assigned to:		CPU Architecture:	Any
Tags:	5.1.25-rc

Description:
When I dropped the mysql.ndb_apply_status system table, there are the following messages in the error log:

080705  9:55:47 [Note] NDB delete table: waiting max 1 sec for delete table ./mysql/ndb_apply_status.  epochs: (0/0,0/0,35492/19)  injector proc_info: Waiting for event from ndbcluster
080705  9:55:48 [ERROR] NDB delete table: ./mysql/ndb_apply_status timed out. Ignoring...

DROP TABLE command took 120 seconds to complete. But as the message said, the table wasn't really deleted. When I restarted the server, it appeared again.

How to repeat:
Simply remove mysql.ndb_apply_status table:

mysql> DROP TABLE mysql.ndb_apply_status;

Then, this command will take 120 sec. You'll see the similar message in your error log on the SQL node.

Suggested fix:
Since it is the system table used by binlog injection thread, shouldn't data nodes return some error when a SQL node attempts to drop it?

assuming solution: silently ignoring drop of needed tables
R3, E3

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".