Bug #49458 Restart types listed by ndb_config are not consistent with the documentation

Submitted: 4 Dec 2009 13:58 Modified: 7 Dec 2009 8:24
Reporter: Sivert Sørumgård Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S2 (Serious)
Version:mysql-5.1-telco-7.0 OS:Any
Assigned to: CPU Architecture:Any
Tags: 5.1.39 ndb-7.0.10

[4 Dec 2009 13:58] Sivert Sørumgård
Description:
When running ndb_config --xml --configinfo on 7.0.10, the restart levels in the output are not the same as those listed in the docs on http://dev.mysql.com/doc/refman/5.1/en/mysql-cluster-params-ndbd.html

E.g., ndb_config lists MaxNoOfConcurrentTransactions as having a default restart type (i.e. node, not initial) while the docs lists this as requiring system restart. There are other inconsistencies too.

How to repeat:
Run ndb_config --xml --configinfo on 7.0.10+

Compare restart types with what's documented.
[7 Dec 2009 8:24] Sveta Smirnova
Thank you for the report.

Verified as described.
[7 Dec 2009 18:35] Jon Stephens
I'll repeat what I said earlier about this here:

Where does ndb_config get its info about required restart types?

How is this information derived?

If this is somehow more accurate than what Serge, Jeb, and I obtained through testing a couple of years ago, then I need to know about it, and where to get it. In which case this is a Docs bug, and it needs to be fixed, and someone needs to tell me where to get the correct info.

In any case, either ndb_config output is wrong or docs are wrong. In either case, we're giving customers wrong info about a critical aspect of Cluster administration, and this is not acceptable.

Raising this to P2/S2 on basis of the foregoing. Let's get some answers and do something about this ASAP.

Portions of this website are copyright © 2001, 2002 The PHP Group

Page generated in 0.052 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.