Bug #26633 Unclear paragraph in cluster docu
Submitted: 26 Feb 2007 12:48 Modified: 5 Mar 2007 7:46
Reporter: Oli Sennhauser Email Updates:
Status: Closed Impact on me:
Category:MySQL Server: Documentation Severity:S3 (Non-critical)
Version:5.0 and 5.1 OS:
Assigned to: Jon Stephens CPU Architecture:Any

[26 Feb 2007 12:48] Oli Sennhauser
On the following page


This paragraph is partly redundant and does not explain the calculation correctly (IMHO):

"This parameter specifies the number of scans possible in the transaction coordinator. If the number of local scan records is not provided, it is calculated as the product of MaxNoOfConcurrentScans and the number of data nodes in the system."

How to repeat:
see above

Suggested fix:
First part is redundant. Second part senseless. It may be that it belongs to MaxNoOfLocalScans???
[26 Feb 2007 14:26] Sveta Smirnova
Thank you for the report.

Verified as described. Quoted test seems to belong to MaxNoOfLocalScans and not to MaxNoOfConcurrentScans
[3 Mar 2007 12:17] Jon Stephens
The text from the URL provided reads: "This parameter is deprecated in MySQL 5.0; you should use MaxNoOfOrderedIndexes and MaxNoOfUniqueHashIndexes instead. ... This parameter is used only by unique hash indexes. There needs to be one record in this pool for each unique hash index defined in the cluster. ... The default value of this parameter is 128."

I don't understand what's going on here.
[5 Mar 2007 7:46] Jon Stephens
Okay, I was confused because you linked to a different section - that paragraph actually appeared in the description of MaxNoOfConcurrentScans (http://dev.mysql.com/doc/refman/5.1/en/mysql-cluster-ndbd-definition.html#mysql-cluster-pa...), and you're right, it belongs to the following item (description of MaxNoOfLocalScans), which is where I've moved it to. (Also in the 4.1 and 5.0 versions of that page.)


Changeset was mysqldoc rev 5167 (commits db was down).