Bug #68634 | DROP/CREATE TABLE running into timeouts on certain api nodes, but not all | ||
---|---|---|---|
Submitted: | 11 Mar 2013 10:59 | Modified: | 14 Mar 2013 13:37 |
Reporter: | Hartmut Holzgraefe | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Cluster: Cluster (NDB) storage engine | Severity: | S3 (Non-critical) |
Version: | 5.5.22-ndb-7.2.6-log | OS: | Linux |
Assigned to: | CPU Architecture: | Any |
[11 Mar 2013 10:59]
Hartmut Holzgraefe
[11 Mar 2013 11:12]
Hartmut Holzgraefe
API nodes are using multiple NDB connections here: ndb-cluster-connection-pool=8 Maybe the problem is related to connection pool handling?
[14 Mar 2013 12:19]
MySQL Verification Team
Hello Hartmut, Thank you for the report. Verified as described. Thanks, Umesh
[14 Mar 2013 12:27]
MySQL Verification Team
error log contents - 7.2.6/10
Attachment: 68634.txt (text/plain), 131.61 KiB.
[14 Mar 2013 13:37]
Hartmut Holzgraefe
Hi Umesh, how did you verify it? Are you able to reproduce it at will?
[2 Apr 2015 16:54]
Odis Yuck
Hello. Now I have problems with same bug. It reproduced even after restart with "--initial" and recovering from NDB backup. Recently I tried new master-master replication with NDB_EPOCH2_TRANS function. I had problems in both clusters, but after removing all data in /var/lib/mysql and starting data nodes with "--initial" one cluster works fine. So, I can fix it now with such strange method, but it was just experimenting. I don't want to face with such problem in production. Is there some progress in solving this issue?
[9 Feb 2018 19:24]
Dev Das
Hi, We are running MySQL cluster (Server version: 5.7.16-ndb-7.5.4-cluster-gpl-log MySQL Cluster Community Server (GPL)) and intermittently get following message in MySQL Error logs:: [Warning] NDB: Failed to release global schema lock, error: (266)Time-out in NDB, probably caused by deadlock. As mentioned this does not happen always, but does happen with 2 conseceutive requests: 2018-02-09T16:26:20.070589Z DROP TABLE IF EXISTS temp_account_pool 2018-02-09T16:26:20.071043Z CREATE TABLE temp_account_pool (...) Is there a proper solution to this? Thanks in advance for any suggestions.