Bug #50188 ndb_config --xml --configinfo: Restart mysqld nodes for a parameter change?
Submitted: 8 Jan 2010 13:52 Modified: 10 Mar 2010 11:00
Reporter: Sivert Sørumgård Email Updates:
Status: Verified Impact on me:
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S4 (Feature request)
Version:7.0.13, all OS:Any
Assigned to: CPU Architecture:Any

[8 Jan 2010 13:52] Sivert Sørumgård
For some parameters in config.ini, all cluster processes should be restarted, including mysqlds. For other parameters, mysqld processes do not need to be restarted. This should be reflected in the output from ndb_config --xml --configinfo. 

See also http://bugs.mysql.com/bug.php?id=47366 (show restart types), http://bugs.mysql.com/bug.php?id=49656 (MCM should not restart mysqld nodes when changing a ndb(mt)d attribute), http://bugs.mysql.com/bug.php?id=49781 (Insufficient restart types for API nodes listed in ConfigInfo.cpp) and http://bugs.mysql.com/bug.php?id=49668 (ndb_config: Need more fine-grained restart impact description). 

How to repeat:
Feature request

Suggested fix:
Add attribute in the xml output for each parameter, e.g. restartmysqld="false". Default should probably be to restart mysqlds.