MySQL Bugs: #47629: error-log to ndbmtd is not informative enough

Bug #47629	error-log to ndbmtd is not informative enough
Submitted:	24 Sep 2009 17:32	Modified:	25 Sep 2009 7:16
Reporter:	Jonas Oreland	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S3 (Non-critical)
Version:	mysql-5.1-telco-7.0	OS:	Any
Assigned to:	Jonas Oreland	CPU Architecture:	Any

Description:
error log generated from ndbmtd has the following "problems"
- version string can be truncated (or not shown) if sufficient no of
  threads are used, this as filename of each of the tracefiles are printed

- if it crashed in any of the execution thread, this is not printed
  this makes one have to scan all files, searching for file that does
  not end with STOP_FOR_CRASH

How to repeat:
crash node, read error log

Suggested fix:
1) print version before listing of tracefiles
2) print thread no that crashed (if available)

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

3037 Jonas Oreland	2009-09-24
      ndb - bug#47629
        Improve content of error log when generated from ndbmtd
        (also fix bug when crash in fs/watch-thread happens, in which
         too much stack is used e.g switch Signal => SignalT<25>)

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

3038 Jonas Oreland	2009-09-24
      ndb - bug#47629
        Improve content of error log when generated from ndbmtd
        (also fix bug when crash in fs/watch-thread happens, in which
         too much stack is used e.g switch Signal => SignalT<25>)

7.0.8 and 7.1

Documented bugfix in the NDB-7.0.8 changelog as follows:

        Two issues with error logs generated by ndbmtd were addressed:

            1. The version string was sometimes truncated, or even not
            shown, depending on the number of threads in use (the more
            threads, the worse the problem). Now the version string is
            shown in full, as well as the filenames for all tracefiles
            (where available).

            2. In the event of a crash, the thread number of the thread
            that crashed was not printed. Now this information is 
            supplied, if available.

Closed.

Pushed into 5.1.37-ndb-7.0.9 (revid:jonas@mysql.com-20090930075942-1q6asjcp0gaeynmj) (version source revid:jonas@mysql.com-20090924181121-c9u0uvtqqsxp3ndu) (merge vers: 5.1.37-ndb-7.0.8) (pib:11)

Pushed into 5.1.35-ndb-7.1.0 (revid:jonas@mysql.com-20090930080049-1c8a8cio9qgvhq35) (version source revid:jonas@mysql.com-20090924183342-t0szmlwi3hrzgw4s) (merge vers: 5.1.35-ndb-7.1.0) (pib:11)