MySQL Bugs: #60119: ndb_cluster_connection_pool status variable value is too high

Bug #60119	ndb_cluster_connection_pool status variable value is too high
Submitted:	14 Feb 2011 7:05	Modified:	7 Mar 2011 12:03
Reporter:	varun deewan	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S3 (Non-critical)
Version:	5.1.51-ndb-7.1.9a	OS:	Other (open suse sles11)
Assigned to:	Maitrayi Sabaratnam	CPU Architecture:	Any
Tags:	ndb_cluster_connection_pool

Description:
in my my.cnf file i have below entries :-

ndb-cluster-connection-pool=4
ndbcluster

but when checking this value in mysql i got below results .. i am not able to understand why ndb_cluster_connection_pool variable value in mysql status is very high.
please check below outputs:

mysql> show variables like 'ndb_clu%';
+-----------------------------+-------+
| Variable_name | Value |
+-----------------------------+-------+
| ndb_cluster_connection_pool | 4 |
+-----------------------------+-------+
1 row in set (0.00 sec)

mysql> show status like 'ndb_clu%';
+-----------------------------+-------------+
| Variable_name | Value |
+-----------------------------+-------------+
| Ndb_cluster_node_id | 9 |
| Ndb_cluster_connection_pool | 17179869184 |
+-----------------------------+-------------+
2 rows in set (0.00 sec)

mysql> 

here is my config.ini file.
------------------------
[TCP DEFAULT]
SendBufferMemory=2M
ReceiveBufferMemory=2M

[NDB_MGMD DEFAULT]
PortNumber=4444
Datadir=/data/mysqlcluster/

[NDB_MGMD]
NodeId=1
Hostname=192.168.56.51
LogDestination=FILE:filename=ndb_1_cluster.log,maxsize=10000000,maxfiles=6
ArbitrationRank=1

[NDBD DEFAULT]
NoOfReplicas=2
Datadir=/data/mysqlcluster/
FileSystemPathDD=/data/mysqlcluster/
DataMemory=1024M
IndexMemory=320M
MaxNoOfExecutionThreads=4
MaxNoOfConcurrentOperations=100000

LockPagesInMainMemory=1

[NDBD]
NodeId=2
Hostname=192.168.56.52

[NDBD]
NodeId=3
Hostname=192.168.56.53

[MYSQLD]
NodeId=6
Hostname=192.168.56.52

[MYSQLD]
NodeId=7
Hostname=192.168.56.53

[MYSQLD]

[MYSQLD]

[MYSQLD]

[MYSQLD]

[MYSQLD]

[MYSQLD]
-------------------------------------
Here is my.cnf file
-------------------------------------

[MYSQLD]
user=mysql
basedir=/usr/local/mysql/
datadir=/data/mysql/
pid-file=mysqld.pid
socket=/data/mysql//mysql.sock
port=3306
ndbcluster
ndb-connectstring="192.168.56.51:4444"
ndb_cluster_connection_pool=4
ndb-autoincrement-prefetch-sz=512
skip-name-resolve
log-err=/data/logs/mysql/error.log
sort_buffer_size = 512K
read_buffer_size = 256K
read_rnd_buffer_size = 512K
thread_cache_size=512
max-connections=500
query-cache-type = 0
query-cache-size = 0
table-cache=512

[mysql_cluster]
ndb-connectstring=192.168.56.51:4444

[MYSQL]
socket=/data/mysql//mysql.sock

[client]
socket=/data/mysql//mysql.sock

# The safe_mysqld script
[safe_mysqld]
log-error=/data/logs/mysql/mysqld.log

[mysqldump]
quick
max_allowed_packet = 16M

[mysql]
no-auto-rehash
# Remove the next comment character if you are not familiar with SQL
#safe-updates

[myisamchk]

[mysqlhotcopy]
#interactive-timeout
----------------------------------------------------------

How to repeat:

Not sure if it could be simulated bu configuring similar cluster at your end.
please try once.

Since this status variable is redundant information from the global config variable ndb_cluster_connection_pool.  Since the config variable is read-only and taken only from the command line option the status variable should actually be removed.

Fix committed: http://lists.mysql.com/commits/132231

Fix is ok.

MTR testcase ndb_basic includes all of the status vars, so will need to be updated to account for this change.

Test updated:
http://lists.mysql.com/commits/132283

Merged in 7.0 and 7.1.

Documented as follows in the NDB 7.0.23 ans 7.1.12 changelogs:

        Formerly, the --ndb-cluster-connection-pool server option 
        set a status variable as well as as a system variable. The 
        status variable has been removed as redundant.

Also noted this in the description of the server option.

Closed.