Bug #56256 | Cluster failure while performing standard rolling restart (increased DataMemory) | ||
---|---|---|---|
Submitted: | 25 Aug 2010 14:44 | Modified: | 25 Aug 2010 14:53 |
Reporter: | Jeffrey R | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Cluster: Cluster (NDB) storage engine | Severity: | S2 (Serious) |
Version: | 5.1.44 | OS: | Linux (Fedora) |
Assigned to: | CPU Architecture: | Any |
[25 Aug 2010 14:44]
Jeffrey R
[25 Aug 2010 14:47]
Andrew Hutchings
Please note that for increasing datamemory you should not start the data nodes with --initial. Can you please send us the file generated by ndb_error_reporter for this?
[25 Aug 2010 14:48]
Jeffrey R
ndbmtd error log
Attachment: ndbmtd_3_logs.tar.gz (application/x-gzip, text), 304.01 KiB.
[25 Aug 2010 14:53]
Andrew Hutchings
This is a gcp_commit based GCP stop. Basically the disks for the data node cannot handle the traffic required when starting the data node. Please see the section on GCP Stop in: http://dev.mysql.com/doc/refman/5.1/en/mysql-cluster-ndbd-definition.html If this does not help please increase TimeBetweenEpochsTimeout: http://dev.mysql.com/doc/refman/5.1/en/mysql-cluster-ndbd-definition.html#ndbparam-ndbd-ti...