| Bug #19045 | No meaningful error message when defining too many nodes | ||
|---|---|---|---|
| Submitted: | 12 Apr 2006 11:58 | Modified: | 2 Nov 2006 5:00 |
| Reporter: | Hartmut Holzgraefe | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Cluster: Cluster (NDB) storage engine | Severity: | S3 (Non-critical) |
| Version: | 4.1, 5.0 | OS: | Any (*) |
| Assigned to: | justin he | CPU Architecture: | Any |
[10 Aug 2006 10:25]
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/10250 ChangeSet@1.2246, 2006-08-10 18:23:52+08:00, root@qa3-104.qa.cn.tlan +2 -0 BUG#19045, No meaningfull error message when defining too many nodes improve error information when too many nodes configured
[11 Aug 2006 5:56]
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/10294 ChangeSet@1.2246, 2006-08-11 13:52:54+08:00, justin.he@qa3-104.qa.cn.tlan +2 -0 BUG#19045, No meaningfull error message when defining too many nodes
[14 Aug 2006 6:44]
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/10334 ChangeSet@1.2246, 2006-08-14 14:42:26+08:00, Justin.He@qa3-104.qa.cn.tlan +2 -0 BUG#19045, No meaningfull error message when defining too many nodes
[14 Aug 2006 10:19]
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/10350 ChangeSet@1.2252, 2006-08-14 18:17:13+08:00, Justin.He@qa3-104.qa.cn.tlan +2 -0 BUG#19045, No meaningfull error message when defining too many nodes
[14 Aug 2006 10:35]
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/10353 ChangeSet@1.2252, 2006-08-14 18:33:41+08:00, Justin.He@qa3-104.qa.cn.tlan +2 -0 BUG#19045, No meaningfull error message when defining too many nodes
[10 Oct 2006 18:26]
Jonas Oreland
pushed into 5.1.12
[1 Nov 2006 14:32]
Jonas Oreland
pushed into 5.0.29 no fix in 4.1
[2 Nov 2006 5:00]
Jon Stephens
Thank you for your bug report. This issue has been committed to our source repository of that product and will be incorporated into the next release.
If necessary, you can access the source repository and build the latest available version, including the bug fix. More information about accessing the source trees is available at
http://dev.mysql.com/doc/en/installing-source.html
Documented bugfix for 5.0.29 & 5.1.12.
[4 Nov 2006 3:08]
Jon Stephens
*Fix for 5.0 documented in 5.0.30 Release Notes.*
Description: When defining more than 64 nodes in the cluster config the 4.1 management server prints the following warning once for each extra node: MgmtSrvr.cpp 461: Warning! Requirement failed but starts anyway. This message does not give any hints at all. The 5.0 management server prints this error instead: Error line 85: Unable to handle deprication, new value not within boundsNodeId Id - [API] starting at line: 84 Error line 85: Could not store previous section of configuration file. Unable to read config file and refuses to start. The 5.0 message has at least some information in it but its still rather confusing: - what has this to do with deprication? - i only have empty [MYSQLD] entries on line 84 and 85, the node Id is implicitly created - what are the bounds the node id is not in? How to repeat: try to start ndb_mgmd with a config like this: [NDBD DEFAULT] NoOfReplicas= 2 datadir=/usr/local/mysql/cluster DataMemory=120M IndexMemory=80M [NDB_MGMD DEFAULT] datadir=/usr/local/mysql/cluster [NDB_MGMD] Hostname=localhost [NDBD] Hostname=localhost [NDBD] Hostname=localhost [MYSQLD] [MYSQLD] [MYSQLD] [MYSQLD] [MYSQLD] [MYSQLD] [MYSQLD] [MYSQLD] [MYSQLD] [MYSQLD] [MYSQLD] [MYSQLD] [MYSQLD] [MYSQLD] [MYSQLD] [MYSQLD] [MYSQLD] [MYSQLD] [MYSQLD] [MYSQLD] [MYSQLD] [MYSQLD] [MYSQLD] [MYSQLD] [MYSQLD] [MYSQLD] [MYSQLD] [MYSQLD] [MYSQLD] [MYSQLD] [MYSQLD] [MYSQLD] [MYSQLD] [MYSQLD] [MYSQLD] [MYSQLD] [MYSQLD] [MYSQLD] [MYSQLD] [MYSQLD] [MYSQLD] [MYSQLD] [MYSQLD] [MYSQLD] [MYSQLD] [MYSQLD] [MYSQLD] [MYSQLD] [MYSQLD] [MYSQLD] [MYSQLD] [MYSQLD] [MYSQLD] [MYSQLD] [MYSQLD] [MYSQLD] [MYSQLD] [MYSQLD] [MYSQLD] [MYSQLD] [MYSQLD] [MYSQLD] [MYSQLD] [MYSQLD] [MYSQLD] [MYSQLD] [MYSQLD] [MYSQLD] Suggested fix: The error message in this case should be something like: To many nodes configured, only up to %d nodes supported.