Bug #30896 | unwanted shutdown of ndb slave cluster | ||
---|---|---|---|
Submitted: | 7 Sep 2007 14:25 | Modified: | 18 Sep 2007 10:00 |
Reporter: | Nicolas Legrand | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Cluster: Replication | Severity: | S1 (Critical) |
Version: | 5.1.20beta | OS: | Linux |
Assigned to: | CPU Architecture: | Any | |
Tags: | dbtup, ndb, replication, salve |
[7 Sep 2007 14:25]
Nicolas Legrand
[8 Sep 2007 21:18]
Hartmut Holzgraefe
To analyze this we need your config.ini and the complete set of node error and trace logs. You can either collect them manually from the cluster nodes or use the ndb_error_reporter tool to do so: http://dev.mysql.com/doc/refman/5.0/en/mysql-cluster-utilities-ndb-error-reporter.html
[18 Sep 2007 10:00]
Nicolas Legrand
It seems that some differences between table on slave and replication might be the cause of that issue.