Bug #48266 Reading too much causes node-crash instead of error message
Submitted: 23 Oct 2009 12:59 Modified: 23 Oct 2009 14:56
Reporter: Jonas Oreland Email Updates:
Status: Closed Impact on me:
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version: OS:Any
Assigned to: Jonas Oreland CPU Architecture:Any

[23 Oct 2009 12:59] Jonas Oreland
If from a ndbapi program one reads the same column more than once,
one could hit the max message size limitation, which should
abort the operation with error code "TRY_TO_READ_TO_MUCH", however
due to a change introduced in 6.3.18, this check was not done correctly
which instead caused node crash

How to repeat:
new test-prg testNdbApi -n ReadColumnDuplicates T6
discovered regression

Suggested fix:
Fix define
[23 Oct 2009 13:00] 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:


3131 Jonas Oreland	2009-10-23
      ndb - bug#48266 - use correct constant for MAX_READ
[23 Oct 2009 13:04] Jonas Oreland
pushed to 6.3.28 and 7.0.9
[23 Oct 2009 14:56] Jon Stephens
Documented bugfix in the NDB-6.3.28 and 7.0.9 changelogs as follows:

        If an NDB API program reads the same column more than once, it
        is possible exceed the maximum allowable message size, in which
        case the operation should be aborted due to NDB error 880
        Tried to read too much - too many getValue
        calls, however due to a change introduced in MySQL
        Cluster NDB 6.3.18, the check for this was not done correctly,
        which instead caused a data node crash.