Bug #37419 | Table disappears with ALTER TABLE | ||
---|---|---|---|
Submitted: | 16 Jun 2008 2:15 | Modified: | 17 Dec 2009 11:27 |
Reporter: | Adam Dixon | 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: | Martin Skold | CPU Architecture: | Any |
Tags: | 6.2.15 |
[16 Jun 2008 2:15]
Adam Dixon
[26 Aug 2008 4:52]
Feelora Gee
hi,guys, how this bug going on?
[28 Aug 2008 7:43]
Martin Skold
This is because of interaction with the autodiscover functionality. Table must be locked for DDL operations in all connected mysqlds while alter table operation is executing.
[28 Aug 2008 7:48]
Martin Skold
Workaround is to set cluster in single user mode during alter table as documentation specifies: http://dev.mysql.com/doc/refman/5.1/en/mysql-cluster-limitations-multiple-nodes.html http://dev.mysql.com/doc/refman/5.1/en/mysql-cluster-single-user-mode.html
[6 Nov 2008 13:32]
Feelora Gee
This problem will reproduce in single user mode.
[14 Nov 2008 11:33]
Bernd Ocklin
Feelora Gee, The above test case should fail in single user mode for host 1 since it will block traffic on machines b) and c). Do you have a test case for us that demonstrates table disappearing in single user mode?
[16 Nov 2008 23:00]
Adam Dixon
Going by how Tomas has described usage of this above, online alter operations should not need single user mode. The test case does include a non-online operation in drop column. So this is not possible to run in this case. I could not repeat this while adding only indexes/columns with null default.
[12 Aug 2009 15:59]
jon stritar
I'm experiencing this bug as well. How do people recommend updating schemas while maintaining availability? Is this just not possible in a high traffic cluster?
[20 Aug 2009 10:06]
Sveta Smirnova
Bug #39033 was marked as duplicate of this one.
[8 Oct 2009 7:28]
Bernd Ocklin
Should be fixed in latest 6.2./6.3 versions with global schema lock. Can you re-test?
[3 Dec 2009 0: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".
[3 Dec 2009 7:46]
Sveta Smirnova
Adam, please re-test this bug.
[7 Dec 2009 4:02]
Adam Dixon
Using 7.0.9 the only error I can get is on a 'selecting' api node the incorrect information in file error, it is a temporary error. This test includes non-online operations, as I stated above.
[7 Dec 2009 7:32]
Jonas Oreland
Hi Adam, can you be be a bit elaborate on the result of testing a newer version. especially, is there still a bug, and if yes, it it same as $subject if yes, no, what is the new bug... /Jonas
[7 Dec 2009 23:54]
Adam Dixon
Hello Jonas, I do not think we have a bug here. The test case also includes non-online operations, as well as the test case no longer produces the numerous other errors seen in the original report. So I do not think we have a bug here.
[17 Dec 2009 11:27]
Martin Skold
Closed due to inability to reproduce anymore.