Bug #37921 | sql node not aware that table does not exist on data nodes | ||
---|---|---|---|
Submitted: | 7 Jul 2008 10:21 | Modified: | 6 Nov 2008 19:50 |
Reporter: | Bogdan Kecman | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Cluster: Cluster (NDB) storage engine | Severity: | S2 (Serious) |
Version: | 6.x.x | OS: | Any |
Assigned to: | Martin Skold | CPU Architecture: | Any |
Tags: | initial |
[7 Jul 2008 10:21]
Bogdan Kecman
[4 Sep 2008 9:07]
Martin Skold
The obvious work around is to do a: show tables; This discovers new tables and removes stale .frm files.
[7 Sep 2008 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/53458 2660 Martin Skold 2008-09-07 Bug #37921 sql node not aware that table does not exist on data nodes: Adding check for stale frm files in mysql_create_table
[6 Nov 2008 19:50]
Jon Stephens
Documented bugfix in the NDB-6.2.16 and NDB-6.3.18 changelogs as follows: After a forced shutdown and initial restart of the cluster, it was possible for SQL nodes to retain .FRM files corresponding to NDBCLUSTER tables that had been dropped, and thus to be unaware that these tables no longer existed. In such cases, attempting to re-create the tables using CREATE TABLE IF NOT EXISTS could fail with a spurious Table ... doesn't exist error.