Bug #45276 ndb_mgmd ingnores --reload if out of order in command line
Submitted: 2 Jun 2009 21:37 Modified: 23 Sep 2009 13:19
Reporter: Jonathan Miller Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:mysql-5.1-telco-7.0 OS:Linux
Assigned to: Magnus Blåudd CPU Architecture:Any

[2 Jun 2009 21:37] Jonathan Miller
Description:
NOTE: ndb_1_config.bin.2 already exists. I made changes and tried to reload.

[ndbdev@ndb3 run]$ /data0/cr_autotest/libexec/ndb_mgmd -f config.ini --reload
2009-06-02 23:31:33 [MgmSrvr] INFO     -- NDB Cluster Management Server. mysql-5.1.34 ndb-7.0.6
2009-06-02 23:31:33 [MgmSrvr] INFO     -- Loaded config from '/data0/cr_autotest//mysql-cluster/ndb_1_config.bin.2'

Notice, ^ no change from bin.2

[ndbdev@ndb3 run]$ /data0/cr_autotest/libexec/ndb_mgmd --reload -f config.ini
2009-06-02 23:31:57 [MgmSrvr] INFO     -- NDB Cluster Management Server. mysql-5.1.34 ndb-7.0.6
2009-06-02 23:31:57 [MgmSrvr] INFO     -- Loaded config from '/data0/cr_autotest//mysql-cluster/ndb_1_config.bin.3'

By changing the position of the --reload I now get my new version.

How to repeat:
See above

Suggested fix:
--reload should be accepted after -f as well as before.
[23 Sep 2009 13:19] Magnus Blåudd
Tried with --reload both before and after -f config.ini and both works. It's normal that the ndb_mgmd start up and read the "old" config.bin file to know what it should change from. Then it read config.ini and if --reload and if !equal does an online config change.