Bug #54342 ndbmtd contention warning shows in ndbd
Submitted: 8 Jun 2010 15:49 Modified: 19 Aug 2010 11:33
Reporter: Andrew Hutchings 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

[8 Jun 2010 15:49] Andrew Hutchings 
Description:
The following warning shows in ndbd but it should be a ndbmtd only warning:

2010-05-20 09:43:58 [ndbd] WARNING -- MaxNoOfExecutionThreads (2) > LockExecuteThreadToCPU count (1), this could cause contention

How to repeat:
.
[17 Aug 2010 10:23] 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/115911

3687 Jonas Oreland	2010-08-17
      ndb - bug#54342 - only print "lockcpu vs maxexecutionthreads"-warning if running ndbmtd
[17 Aug 2010 10:25] Jonas Oreland 
pushed to 6.3.37, 7.0.18 and 7.1.7
[17 Aug 2010 10:25] Bugs System 
Pushed into mysql-5.1-telco-7.0 5.1.47-ndb-7.0.18 (revid:jonas@mysql.com-20100817102144-kcdv8fldyl7nxsz5) (version source revid:jonas@mysql.com-20100817102144-kcdv8fldyl7nxsz5) (merge vers: 5.1.47-ndb-7.0.18) (pib:20)
[19 Aug 2010 11:18] Jon Stephens 
Documented bugfix in the NDB-6.3.37, 7.0.18, and 7.1.7 changelogs, as follows:

      The warning -MaxNoOfExecutionThreads (#) > LockExecuteThreadToCPU 
      count (#), this could cause contention- could be logged when 
      running ndbd, even though the condition described can occur only 
      when using ndbmtd.

Closed.