Bug #39839 some all clusterlog stastics data do not report with node id

• Submitted: 3 Oct 2008 14:25
• Modified: 12 Nov 2008 10:45
• Reporter: Oli Sennhauser
• Status: Closed
• Category: MySQL Cluster: Cluster (NDB) storage engine
• Severity: S3 (Non-critical)
• Version: any
• OS: Any
• Assigned to: Frazer Clement
• CPU Architecture: Any

[3 Oct 2008 14:25] Oli Sennhauser

Description:
if all clusterlog statistics is set to 15 the following data are reported to the cluster log but without node info:

2008-10-03 16:10:38 [MgmSrvr] INFO     -- Mean loop Counter in doJob last 8192 times = 58
2008-10-03 16:10:38 [MgmSrvr] INFO     -- 8192 loops,tot 12205135 usec,exec 587 extra:loops = 0,time 0,const 50
2008-10-03 16:10:39 [MgmSrvr] INFO     -- Mean loop Counter in doJob last 8192 times = 68
2008-10-03 16:10:39 [MgmSrvr] INFO     -- 8192 loops,tot 14172853 usec,exec 887 extra:loops = 0,time 0,const 50

How to repeat:
ndb_mgm> all clusterlog statistics=15

Suggested fix:
2008-10-03 16:10:38 [MgmSrvr] INFO     -- Node 10: Mean loop Counter in doJob last 8192 times = 58
2008-10-03 16:10:38 [MgmSrvr] INFO     -- Node 10: 8192 loops,tot 12205135 usec,exec 587 extra:loops = 0,time 0,const 50
2008-10-03 16:10:39 [MgmSrvr] INFO     -- Node 11: Mean loop Counter in doJob last 8192 times = 68
2008-10-03 16:10:39 [MgmSrvr] INFO     -- Node 11: 8192 loops,tot 14172853 usec,exec 887 extra:loops = 0,time 0,const 50

[22 Oct 2008 11:26] Frazer Clement

Proposed patch to add nodeid to NDBD scheduler report events

Attachment: bug39839.patch (text/x-patch), 562 bytes.

[22 Oct 2008 11:27] Frazer Clement

Proposed patch which ensures event report has nodeid when passing through CMVMI.

[6 Nov 2008 17:58] Bugs System

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/58089

2720 Frazer Clement	2008-11-06
      Bug#39839 some all clusterlog stastics data do not report with node id
      
      Events with no sender's block reference should still indicate the 
      node number from which they originated.

[8 Nov 2008 20:47] Bugs System

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/58253

2725 Frazer Clement	2008-11-08
            Bug#39839 some all clusterlog stastics data do not report with node id
            
            Events with no sender's block reference should still indicate the 
            node number from which they originated.

[8 Nov 2008 22:19] Bugs System

Pushed into 5.1.29-ndb-6.4.0  (revid:[e-mail]-20081108204653-05tg4itnjmt7w0g0) (version source revid:[e-mail]-20081108214303-z8nr2z5c1yccxac8) (pib:5)

[8 Nov 2008 22:43] Bugs System

Pushed into 5.1.29-ndb-6.2.17  (revid:[e-mail]-20081108204653-05tg4itnjmt7w0g0) (version source revid:[e-mail]-20081108204653-05tg4itnjmt7w0g0) (pib:5)

[8 Nov 2008 22:45] Bugs System

Pushed into 5.1.29-ndb-6.3.19  (revid:[e-mail]-20081108204653-05tg4itnjmt7w0g0) (version source revid:[e-mail]-20081108212257-xppq7h6xmg3wduzp) (pib:5)

[12 Nov 2008 10:45] Jon Stephens

Documented in the NDB-6.2.17 and NDB-6.3.19 changelogs as follows:

        Events logged after setting ALL CLUSTERLOG
        STATISTICS=15 in the management client did not always
        include the node ID of the reporting node.

[12 Dec 2008 23:26] Bugs System

Pushed into 6.0.9-alpha  (revid:[e-mail]-20081108204653-05tg4itnjmt7w0g0) (version source revid:[e-mail]-20081209185954-9svcixh2p5hsfi6w) (pib:5)