| Bug #47301 | Wrong error reported when attempting to drop table during backup | ||
|---|---|---|---|
| Submitted: | 14 Sep 2009 8:23 | Modified: | 10 May 2016 7:09 |
| Reporter: | Martin Skold | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Cluster: Cluster (NDB) storage engine | Severity: | S3 (Non-critical) |
| Version: | mysql-5.1-telco-6.2 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
[14 Sep 2009 8:23]
Martin Skold
[14 Sep 2009 8:57]
Susanne Ebrecht
Did you also test this with innodb hot backup? Just to make sure that this is only a cluster bug and not a general bug that we have on all transactional storage engines.
[14 Sep 2009 10:23]
Sveta Smirnova
Thank you for the report. Verified as described.
[10 May 2016 7:09]
Jon Stephens
Documented fix in the NDB 7.5.2 changelog, as follows:
Trying to drop a table during an ongoing backup failed with the
error message -Unknown table-; now, it fails with -Unable to
alter table as backup is in progress-.
Closed.
