Bug #79214 | MaxNoOfExecutionThreads documentation wrong for 7.3.3+ | ||
---|---|---|---|
Submitted: | 10 Nov 2015 21:39 | Modified: | 17 Nov 2015 11:42 |
Reporter: | Jesper wisborg Krogh | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Cluster: Documentation | Severity: | S2 (Serious) |
Version: | 7.3+ | OS: | Any |
Assigned to: | Jon Stephens | CPU Architecture: | Any |
[10 Nov 2015 21:39]
Jesper wisborg Krogh
[10 Nov 2015 21:48]
Jesper wisborg Krogh
Posted by developer: Since changing the number of LDM threads requires at least a system restart (and possibly an initial system restart) this should also be mentioned as an online upgrade limitation.
[10 Nov 2015 21:59]
Jesper wisborg Krogh
Posted by developer: The workaround for doing online upgrades is to change to use ThreadConfig instead of MaxNoOfExecutionThreads and set the ThreadConfig configuration to match the pre-upgrade thread distribution.
[10 Nov 2015 22:14]
Jesper wisborg Krogh
Posted by developer: A similar online upgrade limitation exists for 7.4.3 where the number of LDM threads changed for: * MaxNoOfExecutionThreads = 20-23 (LDM changed from 8 to 10) * MaxNoOfExecutionThreads = 40-47 (LDM changed from 16 to 20) http://dev.mysql.com/doc/refman/5.6/en/mysql-cluster-ndbd-definition.html#ndbparam-ndbmtd-... already reflects this change, but should also be noted in the upgrade documentation.
[17 Nov 2015 11:42]
Jon Stephens
Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly.