Bug #11313 confusing/erroneous 4006 message
Submitted: 14 Jun 2005 12:18 Modified: 15 Sep 2007 12:36
Reporter: Tomas Ulin Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:5.0 (ndbapi)-> OS:Any (any)
Assigned to: Tomas Ulin CPU Architecture:Any

[14 Jun 2005 12:18] Tomas Ulin
Description:

(note that this bug should not occur from the mysqlserver)

error 4006 is given by the cluster when it cannot start more transactions.

This can occur for several reasons:
1. no more transaction records in the transaction cordinator
2. the Ndb object in the api has not been initialized with enough parallellism

Bug:

It is not possible/hard to to determing which is the real error since they give the same errormessage

How to repeat:
above

Suggested fix:
make two different error messages for the two types of errors
[7 Sep 2007 9:05] Tomas Ulin
upped prio since it now causes pushbuild failures...
[7 Sep 2007 9:07] 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/33890

ChangeSet@1.2557, 2007-09-07 11:15:07+02:00, tomas@whalegate.ndb.mysql.com +3 -0
  Bug #11313 confusing/erroneous 4006 message
[14 Sep 2007 10:16] Tomas Ulin
won't fix in 5.0
[14 Sep 2007 16:26] Bugs System
Pushed into 5.1.23-beta
[15 Sep 2007 12:36] Jon Stephens
Thank you for your bug report. This issue has been committed to our source repository of that product and will be incorporated into the next release.

If necessary, you can access the source repository and build the latest available version, including the bug fix. More information about accessing the source trees is available at

    http://dev.mysql.com/doc/en/installing-source.html

Documented bugfix in 5.1.23 changelog.
[21 Sep 2007 8:19] Jon Stephens
Also documented in mysql-5.1.22-ndb-6.2.6 changelog.