Bug #40738 DROP DATABASE on Cluster not truely distributed
Submitted: 14 Nov 2008 12:49 Modified: 25 Apr 2009 11:16
Reporter: Johan Andersson Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version: OS:Any
Assigned to: CPU Architecture:Any

[14 Nov 2008 12:49] Johan Andersson 
Description:
DROP DATABASE on Cluster must either
1) DROP the database on _all_ Mysql Servers
or
2) DROP the database on none of the MySQL Servers

Consider a Cluster opf X data nodes and Y mysql servers.
* You have created a database
* You have created a view (on all Y mysql servers) -->  views have a frm file.

Now DROP DATABASE should remove the complete database on _all_ mysql servers connected to it (or nothing at all), not only on the mysql server where you issued the DROP DATABASE command. All other options are not good as it will leave the database in an inconsistent state.

How to repeat:
-

Suggested fix:
-
[25 Mar 2009 11:16] Jonathan Miller 
What version?
[25 Apr 2009 23:00] Bugs System 
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".