| Bug #23887 | ndb_config does not work when using 2 mgm servers and node-ids | ||
|---|---|---|---|
| Submitted: | 2 Nov 2006 15:31 | Modified: | 11 Dec 2006 7:52 |
| Reporter: | Jim Dowling | ||
| Status: | Closed | ||
| Category: | Server: Cluster | Severity: | S1 (Critical) |
| Version: | 5.1.12 | OS: | Linux (linux (ubuntu)) |
| Assigned to: | Hartmut Holzgraefe | Target Version: | |
| Tags: | ndb_config, cluster | ||
[2 Nov 2006 15:31]
Jim Dowling
[2 Nov 2006 15:39]
Jim Dowling
In the previous report, I noticed only one of my ndb_mgmds was running. However, the problem still occurs when i have 2 mgmds running. Note: there is no problem running ndb_config with only a single ndb_mgmd, and we had no problems with 5.1.11. ndb_mgm> show Connected to Management Server at: localhost:23131 Cluster Configuration --------------------- [ndbd(NDB)] 2 node(s) id=1 @127.0.0.1 (Version: 5.1.12, Nodegroup: 0, Master) id=2 @127.0.0.1 (Version: 5.1.12, Nodegroup: 0) [ndb_mgmd(MGM)] 2 node(s) id=62 @127.0.0.1 (Version: 5.1.12) id=63 @127.0.0.1 (Version: 5.1.12) [mysqld(API)] 16 node(s) id=46 (not connected, accepting connect from any host) id=47 (not connected, accepting connect from any host) id=48 @127.0.0.1 (Version: 5.1.12) id=49 (not connected, accepting connect from any host) id=50 (not connected, accepting connect from any host) id=51 (not connected, accepting connect from any host) id=52 (not connected, accepting connect from any host) id=53 (not connected, accepting connect from any host) id=54 (not connected, accepting connect from any host) id=55 (not connected, accepting connect from any host) id=56 (not connected, accepting connect from any host) id=57 (not connected, accepting connect from any host) id=58 (not connected, accepting connect from any host) id=59 (not connected, accepting connect from any host) id=60 (not connected, accepting connect from any host) id=61 (not connected, accepting connect from any host) mysql@jdowling-laptop:/var/lib/mysql-cluster$ ndb_config --ndb-connectstring="nodeid=50:localhost:23131,localhost:23132" -q Diskless Unable to connect with connect string: nodeid=0,localhost:1186 Retrying every 5 seconds. Attempts left: 2
[2 Nov 2006 22:05]
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/14774 ChangeSet@1.2282, 2006-11-02 22:05:02+01:00, hartmut@walhalla.site +1 -0 Fix for Bug #23887 (Introduced by Bugfix #22295)
[2 Nov 2006 22:17]
Hartmut Holzgraefe
parsing the command line option is indeed broken but taking the connect string from the environment works so the following can be used as a workaround: NDB_CONNECTSTRING="localhost:23131,localhost:23132" ndb_config -q Diskless
[13 Nov 2006 17:05]
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/15251 ChangeSet@1.2284, 2006-11-13 17:04:40+01:00, hartmut@mysql.com +1 -0 Fix for Bug #23887 (Introduced by Bugfix #22295)
[11 Dec 2006 7:41]
Jon Stephens
Please note: the 5.0 Manual states that the NDB_CONNECTSTRING environment variable is deprecated and should no longer be used; see http://dev.mysql.com/doc/refman/5.0/en/mysql-cluster-connectstring.html fro details.
[11 Dec 2006 7:52]
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.32 and 5.1.15.
