MySQL Bugs: #70849: unable to drop and create existing ndb table with foregin keys

Bug #70849	unable to drop and create existing ndb table with foregin keys
Submitted:	7 Nov 2013 5:31	Modified:	29 Sep 2020 15:44
Reporter:	prasanth katta	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	Tests: Cluster	Severity:	S7 (Test Cases)
Version:	mysql-5.6.11 ndb-7.3.2	OS:	Linux (Ubuntu 12.04 LTS)
Assigned to:	MySQL Verification Team	CPU Architecture:	Any

Description:
we have a schema with 399 ndb engine tables and when trying to update some around 30 table to the existing schema with the same ndb engine at some table we are facing with the error saying "ERROR 1050 (42S01) at line 878: Table 'xxxx' already exists" so we tried to drop those particular table but no luck getting the same error .

Note :- mysql -uxx -pxx schema name < 30tables.sql (this is how we are updating to the schema)

Note :- this issue is only for the tables with foreign keys during update to existing schema.

here are the steps how we tried to drop those tables.

1. first we deleted the foreign key and tried to drop the tables then those table disappears from the table list again reappears once we restart the ndb mgm.

2. tried to delete the table through the "ndb_drop_table -c connect_string tbl_name -d db_name" command but the same.

3.third we tried to delete the .ndb and .frm files from the schema data dirs but the same .

4. forth we tried to delete the files manually for data dirs and restarted the ndb and mysqld

a. command used to restart "node id" restart -f.

5. now we tried to restart the ndb with --initial command even though no luck.

thanks in advance...

How to repeat:
take a schema with 399 ndb engine tables and try to update around 30 table and some with 'foreign keys' to the existing schema with the same ndb engine then you should be facing with the error saying "ERROR 1050 (42S01) at line 878: Table 'xxxx' already exists" so try to drop those particular tables and see...

ndb error report

Attachment: ndb_2_error.log (text/x-log), 12.25 KiB.

log file one

Attachment: ndb_2_out.log (text/x-log), 1.67 MiB.

log file two

Attachment: ndb_2_trace.log.1 (application/octet-stream, text), 961.77 KiB.

log file three

Attachment: ndb_2_trace.log.2 (application/octet-stream, text), 1.28 MiB.

log file

Attachment: ndb_2_trace.log.next (application/octet-stream, text), 1 bytes.

can you please provide update on this ...it has been a month....

not reproducible with any modern mysql Cluster release