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

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

Proposed patch to add nodeid to NDBD scheduler report events

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

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

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.

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.

Pushed into 5.1.29-ndb-6.4.0  (revid:frazer@mysql.com-20081108204653-05tg4itnjmt7w0g0) (version source revid:frazer@mysql.com-20081108214303-z8nr2z5c1yccxac8) (pib:5)

Pushed into 5.1.29-ndb-6.2.17  (revid:frazer@mysql.com-20081108204653-05tg4itnjmt7w0g0) (version source revid:frazer@mysql.com-20081108204653-05tg4itnjmt7w0g0) (pib:5)

Pushed into 5.1.29-ndb-6.3.19  (revid:frazer@mysql.com-20081108204653-05tg4itnjmt7w0g0) (version source revid:frazer@mysql.com-20081108212257-xppq7h6xmg3wduzp) (pib:5)

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.

Pushed into 6.0.9-alpha  (revid:frazer@mysql.com-20081108204653-05tg4itnjmt7w0g0) (version source revid:tomas.ulin@sun.com-20081209185954-9svcixh2p5hsfi6w) (pib:5)