MySQL Bugs: #45622: CLUSTERLOG INFO does not change logging threshold

Bug #45622	CLUSTERLOG INFO does not change logging threshold
Submitted:	19 Jun 2009 16:27	Modified:	2 Nov 2009 10:10
Reporter:	Rene' Cannao'	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S3 (Non-critical)
Version:	mysql-5.1-telco-6.3	OS:	Linux
Assigned to:	Jonas Oreland	CPU Architecture:	Any
Tags:	cluster 6.3.24-com 6.3.24-gpl, log

Description:
ALL CLUSTERLOG INFO=15 does not trigger the logging of all INFO messages.

Verified with:
mysql-cluster-com-6.3.24-linux-i686-glibc23.tar.gz
mysql-cluster-gpl-6.3.24-linux-i686-glibc23.tar.gz

How to repeat:
All the procedure to repeat it, from the installation and the configuration.

MyHostname:~# cd /tmp
MyHostname:/tmp# tar -C /usr/local -zxf mysql-cluster-com-6.3.24-linux-i686-glibc23.tar.gz 
MyHostname:/tmp# ln -s /usr/local/mysql-cluster-com-6.3.24-linux-i686-glibc23 /usr/local/mysql-cluster

MyHostname:/tmp# mkdir /var/lib/mysql-cluster
MyHostname:/tmp# cd /var/lib/mysql-cluster

MyHostname:/var/lib/mysql-cluster# vim config.ini

NDBD DEFAULT]
NoOFReplicas=2
IndexMemory=18M
DataMemory=64M

[NDB_MGMD DEFAULT]
LogDestination=FILE:filename=/opt/mysql/mgm/cluster.log,maxsize=10M,maxfiles=10

[NDB_MGMD]
Id=1
HostName=127.0.0.1
DataDir=/opt/mysql/mgm

[NDBD]
Id=3
HostName=127.0.0.1
DataDir=/opt/mysql/ndb

[NDBD]
Id=4
HostName=127.0.0.1
DataDir=/opt/mysql/ndb

[NDBD]
Id=5
HostName=127.0.0.1
DataDir=/opt/mysql/ndb

[NDBD]
Id=6
HostName=127.0.0.1
DataDir=/opt/mysql/ndb

[MYSQLD]
Id=11

[MYSQLD]
Id=12

MyHostname:/var/lib/mysql-cluster# vim /etc/my.cnf

[mysqld]
ndbcluster

[mysql_cluster]
ndb-connectstring=127.0.0.1

MyHostname:/var/lib/mysql-cluster# mkdir -p /opt/mysql/ndb
MyHostname:/var/lib/mysql-cluster# mkdir -p /opt/mysql/mgm

MyHostname:/var/lib/mysql-cluster# /usr/local/mysql-cluster/bin/ndb_mgmd -f /var/lib/mysql-cluster/config.ini

MyHostname:/var/lib/mysql-cluster# /usr/local/mysql-cluster/bin/ndbd --ndb-nodeid=3
MyHostname:/var/lib/mysql-cluster# /usr/local/mysql-cluster/bin/ndbd --ndb-nodeid=4
MyHostname:/var/lib/mysql-cluster# /usr/local/mysql-cluster/bin/ndbd --ndb-nodeid=5
MyHostname:/var/lib/mysql-cluster# /usr/local/mysql-cluster/bin/ndbd --ndb-nodeid=6

MyHostname:/var/lib/mysql-cluster# /usr/local/mysql-cluster/bin/ndb_mgm -e show
Connected to Management Server at: 127.0.0.1:1186
Cluster Configuration
---------------------
[ndbd(NDB)]	4 node(s)
id=3	@127.0.0.1  (mysql-5.1.32 ndb-6.3.24, Nodegroup: 0, Master)
id=4	@127.0.0.1  (mysql-5.1.32 ndb-6.3.24, Nodegroup: 0)
id=5	@127.0.0.1  (mysql-5.1.32 ndb-6.3.24, Nodegroup: 1)
id=6	@127.0.0.1  (mysql-5.1.32 ndb-6.3.24, Nodegroup: 1)

[ndb_mgmd(MGM)]	1 node(s)
id=1	@127.0.0.1  (mysql-5.1.32 ndb-6.3.24)

[mysqld(API)]	2 node(s)
id=11 (not connected, accepting connect from any host)
id=12 (not connected, accepting connect from any host)

MyHostname:/var/lib/mysql-cluster# /usr/local/mysql-cluster/bin/ndb_mgm

ndb_mgm> ALL CLUSTERLOG INFO=15
Executing CLUSTERLOG INFO=15 on node 3 OK!
Executing CLUSTERLOG INFO=15 on node 4 OK!
Executing CLUSTERLOG INFO=15 on node 5 OK!
Executing CLUSTERLOG INFO=15 on node 6 OK!

MyHostname:/var/lib/mysql-cluster# tail -n 30 /opt/mysql/mgm/cluster.log 
2009-06-19 15:20:27 [MgmSrvr] INFO     -- Node 4: Start phase 101 completed (initial start)
2009-06-19 15:20:27 [MgmSrvr] INFO     -- Node 4: Started (mysql-5.1.32 ndb-6.3.24)
2009-06-19 15:20:27 [MgmSrvr] INFO     -- Node 5: Start phase 8 completed (initial start)
2009-06-19 15:20:27 [MgmSrvr] INFO     -- Node 5: Start phase 9 completed (initial start)
2009-06-19 15:20:27 [MgmSrvr] INFO     -- Node 5: Start phase 100 completed (initial start)
2009-06-19 15:20:27 [MgmSrvr] INFO     -- Node 5: Start phase 101 completed (initial start)
2009-06-19 15:20:27 [MgmSrvr] INFO     -- Node 5: Started (mysql-5.1.32 ndb-6.3.24)
2009-06-19 15:20:27 [MgmSrvr] INFO     -- Node 6: Start phase 8 completed (initial start)
2009-06-19 15:20:27 [MgmSrvr] INFO     -- Node 6: Start phase 9 completed (initial start)
2009-06-19 15:20:27 [MgmSrvr] INFO     -- Node 6: Start phase 100 completed (initial start)
2009-06-19 15:20:27 [MgmSrvr] INFO     -- Node 6: Start phase 101 completed (initial start)
2009-06-19 15:20:27 [MgmSrvr] INFO     -- Node 6: Started (mysql-5.1.32 ndb-6.3.24)
2009-06-19 15:20:28 [MgmSrvr] INFO     -- Node 3: Node 1: API mysql-5.1.32 ndb-6.3.24
2009-06-19 15:20:28 [MgmSrvr] INFO     -- Node 4: Node 1: API mysql-5.1.32 ndb-6.3.24
2009-06-19 15:20:28 [MgmSrvr] INFO     -- Node 5: Node 1: API mysql-5.1.32 ndb-6.3.24
2009-06-19 15:20:28 [MgmSrvr] INFO     -- Node 6: Node 1: API mysql-5.1.32 ndb-6.3.24
2009-06-19 15:20:28 [MgmSrvr] INFO     -- Node 3: Communication to Node 11 opened
2009-06-19 15:20:28 [MgmSrvr] INFO     -- Node 3: Communication to Node 12 opened
2009-06-19 15:20:28 [MgmSrvr] INFO     -- Node 4: Prepare arbitrator node 1 [ticket=583600010ef80e35]
2009-06-19 15:20:28 [MgmSrvr] INFO     -- Node 5: Prepare arbitrator node 1 [ticket=583600010ef80e35]
2009-06-19 15:20:28 [MgmSrvr] INFO     -- Node 5: Communication to Node 11 opened
2009-06-19 15:20:28 [MgmSrvr] INFO     -- Node 5: Communication to Node 12 opened
2009-06-19 15:20:28 [MgmSrvr] INFO     -- Node 6: Prepare arbitrator node 1 [ticket=583600010ef80e35]
2009-06-19 15:20:28 [MgmSrvr] INFO     -- Node 6: Communication to Node 11 opened
2009-06-19 15:20:28 [MgmSrvr] INFO     -- Node 6: Communication to Node 12 opened
2009-06-19 15:20:28 [MgmSrvr] INFO     -- Node 4: Communication to Node 11 opened
2009-06-19 15:20:28 [MgmSrvr] INFO     -- Node 4: Communication to Node 12 opened
2009-06-19 15:20:28 [MgmSrvr] INFO     -- Node 3: Started arbitrator node 1 [ticket=583600010ef80e35]
2009-06-19 16:18:47 [MgmSrvr] INFO     -- Node 3: Local checkpoint 2 started. Keep GCI = 1 oldest restorable GCI = 2
2009-06-19 17:17:09 [MgmSrvr] INFO     -- Node 3: Local checkpoint 3 started. Keep GCI = 1710 oldest restorable GCI = 3

Suggested fix:
Make CLUSTERLOG INFO=15 logs all INFO messages.

Seem to work on an instance compiled from source with:
 ./configure  --with-plugins=innobase,ndbcluster --with-debug --with-ssl
So probably is a compiling issue.

The "SendHeartbeat" log-message is only enabled in debug-build
(#ifdef VM_TRACE) cause it might flood system...

Why do you need it?

(and this has nothing todo with "logging threshold")

please supply feedback

/Jonas

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".