Bug #47530 Node restart fails with ndbmtd and >2 replicas
| Submitted: | 23 Sep 2009 0:01 | Modified: | 23 Sep 2009 9:56 |
|---|---|---|---|
| Reporter: | David Enbal | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Cluster: Cluster (NDB) storage engine | Severity: | S1 (Critical) |
| Version: | 7.0.7 | OS: | Any |
| Assigned to: | Jonas Oreland | CPU Architecture: | Any |
[23 Sep 2009 0:01]
David Enbal
[23 Sep 2009 5:43]
Jonas Oreland
ndb_error_reporter
[23 Sep 2009 6:05]
David Enbal
I've just uploaded ndb_error_report_20090923085331.tar.bz2 to your FTP. BTW - I just changed the configuration of the cluster to work with only 2 data node (and 2 replicas instead of 3) and everything works like a charm.
[23 Sep 2009 8:08]
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/commits/84256 3032 Jonas Oreland 2009-09-23 ndb - bug#47530 - 3 (or more) replica with ndbmtd, signal sent to proxy instead of instance
[23 Sep 2009 8:10]
Jonas Oreland
pushed to 7.0.8 and 7.1
[23 Sep 2009 9:56]
Jon Stephens
Documented bugfix in the NDB-7.0.8 changelog as follows:
When using multi-threade data nodes (ndbmtd) with NoOfReplicas
set to a value greater than 2, attempting to restart any of the
data nodes caused a forced shutdown of the entire cluster.
Closed.
[30 Sep 2009 8:14]
Bugs System
Pushed into 5.1.37-ndb-7.0.9 (revid:jonas@mysql.com-20090930075942-1q6asjcp0gaeynmj) (version source revid:jonas@mysql.com-20090923080856-nieqdjupo5pm6k91) (merge vers: 5.1.37-ndb-7.0.8) (pib:11)
[30 Sep 2009 8:15]
Bugs System
Pushed into 5.1.35-ndb-7.1.0 (revid:jonas@mysql.com-20090930080049-1c8a8cio9qgvhq35) (version source revid:jonas@mysql.com-20090923080935-lisreez3v0irakzz) (merge vers: 5.1.35-ndb-7.1.0) (pib:11)
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.040 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.