During Node Restart, mysqld Shows: Error "711 System busy with node restart, schema operations not allowed" + Warning "Could not acquire global schema lock (266)Time-out in NDB" (Doc ID 1360809.1)

Last updated on JUNE 18, 2016

Applies to:

MySQL Cluster - Version 7.0 to 7.1 [Release 7.0 to 7.1]
Information in this document applies to any platform.

Symptoms

When attempting to start the cluster, the following error occurs on the SQL nodes:

110901 10:31:26 [Warning] NDB : Tables not available after 15 seconds. Consider increasing --ndb-wait-setup value
110901 10:31:26 [Note] /opt/mysql/mysql/bin/mysqld: ready for connections.
Version: '5.1.51-ndb-7.1.9a-cluster-com-log' socket: '/tmp/mysql.sock' port: 3306 MySQL Cluster Server (Commercial)
110901 10:34:02 [Note] table './mysql/ndb_apply_status' opened read only
110901 10:34:16 [Note] table './mydb/table1' opened read only
110901 10:42:35 [Note] NDB Binlog: DISCOVER TABLE Event: REPL$mysql/ndb_schema
110901 10:58:32 [ERROR] NDB Binlog: ndbevent->execute failed for REPL$mysql/ndb_schema; 711 System busy with node restart, schema operations not allowed
110901 10:58:32 [ERROR] NDB Binlog:FAILED CREATE (DISCOVER) EVENT OPERATIONS Event: REPL$mysql/ndb_schema
110901 11:16:53 [Warning] NDB: Could not acquire global schema lock (266)Time-out in NDB, probably caused by deadlock
110901 11:58:21 [Warning] NDB: Could not acquire global schema lock (266)Time-out in NDB, probably caused by deadlock

Changes

Value set on --ndb-wait-setup lower than the Data node start time.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms