Bug #18561 CR: cluster restart fills MySQLD error log w/ Could not get apply status share

• Submitted: 27 Mar 2006 22:09
• Modified: 23 Jun 2006 20:11
• Reporter: Jonathan Miller
• Status: Can't repeat
• Category: MySQL Cluster: Replication
• Severity: S3 (Non-critical)
• Version: 5.1.9
• OS: Linux (Linux 32 Bit OS)
• Assigned to: Jonathan Miller
• CPU Architecture: Any

[27 Mar 2006 22:09] Jonathan Miller

Description:
Restarting cluster filled mysqld error log with:

060327 23:32:39 [ERROR] NDB: Could not get apply status share
060327 23:32:39 [ERROR] NDB: Could not get apply status share
060327 23:32:39 [ERROR] NDB: Could not get apply status share
060327 23:32:39 [ERROR] NDB: Could not get apply status share
060327 23:32:39 [ERROR] NDB: Could not get apply status share
060327 23:32:39 [ERROR] NDB: Could not get apply status share
060327 23:32:39 [ERROR] NDB: Could not get apply status share
060327 23:32:39 [ERROR] NDB: Could not get apply status share
060327 23:32:39 [ERROR] NDB: Could not get apply status share
060327 23:32:39 [ERROR] NDB: Could not get apply status share
060327 23:32:39 [ERROR] NDB: Could not get apply status share
060327 23:32:39 [ERROR] NDB: Could not get apply status share
060327 23:32:39 [ERROR] NDB: Could not get apply status share
060327 23:32:39 [ERROR] NDB: Could not get apply status share
060327 23:32:39 [ERROR] NDB: Could not get apply status share
060327 23:32:39 [ERROR] NDB: Could not get apply status share
060327 23:32:39 [ERROR] NDB: Could not get apply status share
060327 23:32:39 [ERROR] NDB: Could not get apply status share
060327 23:32:39 [ERROR] NDB: Could not get apply status share
060327 23:32:39 [ERROR] NDB: Could not get apply status share
060327 23:32:39 [ERROR] NDB: Could not get apply status share
060327 23:32:39 [ERROR] NDB: Could not get apply status share
060327 23:32:39 [ERROR] NDB: Could not get apply status share
060327 23:32:39 [ERROR] NDB: Could not get apply status share
060327 23:32:39 [ERROR] NDB: Could not get apply status share

This is not the main mysqld process for the master cluster but rather other mysqld processes attached to the master cluster.

How to repeat:
No sure