Bug #11367 Error message "Can't create table '." floods mysqld error log
Submitted: 15 Jun 2005 23:10 Modified: 13 Sep 2005 13:40
Reporter: Jonathan Miller Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S2 (Serious)
Version:5.1-wl2325 OS:Linux (Linux)
Assigned to: Tomas Ulin CPU Architecture:Any

[15 Jun 2005 23:10] Jonathan Miller 
Description:
Due to Bug #11366 the mysqld process is restarted. When it restarted it is trying to create the apply_status table. Since the cluster is not up it can not create the table. The following error message is inserted into the error log ever one second.

050616  0:59:55 [Note] NDB: Creating cluster_replication.apply_status
050616  0:59:55 [ERROR] NDB: CREATE TABLE IF NOT EXISTS cluster_replication.apply_status ( server_id INT UNSIGNED NOT NULL, epoch BIGINT UNSIGNED NOT NULL,  PRIMARY KEY USING HASH (server_id) ) ENGINE=NDB: error Can't create table './cluster_replication/apply_status.frm' (errno: 4009) 1005 1 1
050616  0:59:56 [Note] NDB: Creating cluster_replication.apply_status
050616  0:59:56 [ERROR] NDB: CREATE TABLE IF NOT EXISTS cluster_replication.apply_status ( server_id INT UNSIGNED NOT NULL, epoch BIGINT UNSIGNED NOT NULL,  PRIMARY KEY USING HASH (server_id) ) ENGINE=NDB: error Can't create table './cluster_replication/apply_status.frm' (errno: 4009) 1005 1 1
050616  0:59:57 [Note] NDB: Creating cluster_replication.apply_status
050616  0:59:57 [ERROR] NDB: CREATE TABLE IF NOT EXISTS cluster_replication.apply_status ( server_id INT UNSIGNED NOT NULL, epoch BIGINT UNSIGNED NOT NULL,  PRIMARY KEY USING HASH (server_id) ) ENGINE=NDB: error Can't create table './cluster_replication/apply_status.frm' (errno: 4009) 1005 1 1

How to repeat:
Follow steps in Bug #11366

Suggested fix:
I think writting the error message once should be enough
[13 Sep 2005 8:00] 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/internals/29712