Bug #47316 | Using two management servers does not work | ||
---|---|---|---|
Submitted: | 15 Sep 2009 9:14 | Modified: | 16 Sep 2009 13:18 |
Reporter: | Johan Andersson | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Cluster: Cluster (NDB) storage engine | Severity: | S2 (Serious) |
Version: | mysql-5.1-telco-7.0.8 (bzr) | OS: | Linux |
Assigned to: | Magnus Blåudd | CPU Architecture: | Any |
Tags: | ndb_mgmd |
[15 Sep 2009 9:14]
Johan Andersson
[15 Sep 2009 9:45]
Sveta Smirnova
Thank you for the report. I can not repeat described behavior if start ndb_mgmd with --ndb-nodeid: $$BASEDIR/libexec/ndb_mgmd -f etc/ndb_mgmd.cfg 2009-09-15 11:42:15 [MgmSrvr] INFO -- NDB Cluster Management Server. mysql-5.1.37 ndb-7.0.8 2009-09-15 11:42:15 [MgmSrvr] INFO -- The default config directory '/users/ssmirnova/blade12/build/mysql-5.1-telco-7.0//mysql-cluster' does not exist. Trying to create it... 2009-09-15 11:42:15 [MgmSrvr] INFO -- Sucessfully created config directory 2009-09-15 11:42:15 [MgmSrvr] INFO -- Reading cluster configuration from 'etc/ndb_mgmd.cfg' 2009-09-15 11:42:15 [MgmSrvr] ERROR -- Could not determine which nodeid to use for this node. Specify it with --ndb-nodeid=<nodeid> on command line $$BASEDIR/libexec/ndb_mgmd -f etc/ndb_mgmd.cfg --ndb-nodeid=1 2009-09-15 11:42:21 [MgmSrvr] INFO -- NDB Cluster Management Server. mysql-5.1.37 ndb-7.0.8 2009-09-15 11:42:21 [MgmSrvr] INFO -- Reading cluster configuration from 'etc/ndb_mgmd.cfg' $$BASEDIR/libexec/ndb_mgmd -f etc/ndb_mgmd.cfg --ndb-nodeid=2 2009-09-15 11:42:25 [MgmSrvr] INFO -- NDB Cluster Management Server. mysql-5.1.37 ndb-7.0.8 2009-09-15 11:42:25 [MgmSrvr] INFO -- Reading cluster configuration from 'etc/ndb_mgmd.cfg' ... $$BASEDIR/bin/ndb_mgm --ndb-mgmd-host=127.0.0.1:35128 -- NDB Cluster -- Management Client -- ndb_mgm> show Connected to Management Server at: 127.0.0.1:35128 Cluster Configuration --------------------- [ndbd(NDB)] 2 node(s) id=3 @127.0.0.1 (mysql-5.1.37 ndb-7.0.8, Nodegroup: 0, Master) id=4 @127.0.0.1 (mysql-5.1.37 ndb-7.0.8, Nodegroup: 0) [ndb_mgmd(MGM)] 2 node(s) id=1 @127.0.0.1 (mysql-5.1.37 ndb-7.0.8) id=2 @127.0.0.1 (mysql-5.1.37 ndb-7.0.8) [mysqld(API)] 4 node(s) id=5 (not connected, accepting connect from localhost) id=6 (not connected, accepting connect from localhost) id=7 (not connected, accepting connect from localhost) id=8 (not connected, accepting connect from localhost) Please check if this solves problem in your case as well.
[15 Sep 2009 12:17]
Bernd Ocklin
Same happens with only one ndb_mgmd: ndb_mgmd -f file stop ndb_mgmd restart ndb_mgmd -f same-file With or without --reload --initial fails. And --node-id was not required beforehand.
[15 Sep 2009 19:07]
Magnus Blåudd
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/83321
[15 Sep 2009 19:09]
Magnus Blåudd
Regression caused by new version of NdbDir::next_file iterator. Never released.
[16 Sep 2009 8:23]
Magnus Blåudd
Pushed to 7.0 and 7.1.
[16 Sep 2009 8:23]
Magnus Blåudd
Pushed to 7.0 and 7.1
[16 Sep 2009 8:31]
Johan Andersson
thanks! It works now! -johan
[16 Sep 2009 13:18]
Jon Stephens
Didn't appear in release per developer comments, no changelog entry needed. Closed without further action.