Bug #42765 ndbmtd - various config variables are multiplied with no of LQH's

Submitted:	11 Feb 2009 14:13	Modified:	11 Feb 2009 17:16
Reporter:	Jonas Oreland	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S3 (Non-critical)
Version:	6.4	OS:	Any
Assigned to:	Jonas Oreland	CPU Architecture:	Any

Description:
If using more than 1 LQH,
then the following parameters are allocated independently by the
different LQH's, causing net allocation to be bigger than anticipated.

IndexMemory
MaxNoOfLocalOperations
MaxNoOfLocalScans

How to repeat:
start ndbmtd

Suggested fix:
divide them by no of LQH instances

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/65915

3255 Jonas Oreland	2009-02-11
      ndb - bug#42765 - divide IndexMemory by no of LQH instances

Pushed into 5.1.31-ndb-6.4.3 (revid:jonas@mysql.com-20090211150728-xs02e448s5bb64q3) (version source revid:jonas@mysql.com-20090211142606-38zchkxvqx6uuutz) (merge vers: 5.1.31-ndb-6.4.3) (pib:6)

Documented in the NDB-6.4.3 changelog as follows:

        When using multi-threaded data nodes, IndexMemory,
        MaxNoOfLocalOperations, and MaxNoOfLocalScans were effectively
        multiplied by the number of local query handlers in use by each
        ndbmtd instance.

Page generated in 0.051 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.