Bug #39518 Incorrectly handled resource shortage during create unique index

• Submitted: 18 Sep 2008 14:25
• Modified: 19 Sep 2008 13:37
• Reporter: Jonas Oreland
• Status: Closed
• Category: MySQL Cluster: Cluster (NDB) storage engine
• Severity: S3 (Non-critical)
• OS: Any
• Assigned to: Jonas Oreland
• CPU Architecture: Any

[18 Sep 2008 14:25] Jonas Oreland

Description:
When running bug#39450, the mysqld just hanged (it leaked), but the 
ndbd kernel did not report back the leak correctly...

This patches fixes so that if there is a resource shortage in SUMA
it will be reported back to create unique index

How to repeat:
run 39450 prior to the bug-fix
notice that it will hang after 255 iteration (default config)

Suggested fix:
report back that it's out of resources

[18 Sep 2008 14:26] 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/54307

2667 Jonas Oreland	2008-09-18
      ndb - bug#39518 - report error back on SUB_CREATE_REF

[18 Sep 2008 14:36] 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/54313

2667 Jonas Oreland	2008-09-18
      ndb - bug#39518 - report error back on SUB_CREATE_REF

[18 Sep 2008 16:22] Jonas Oreland

pushed to 6.2 6.3 and 6.4

[19 Sep 2008 13:37] Jon Stephens

Documented in the NDB 6.2.16 and 6.3.18 as follows:

        Creating a unique index on an NDBCLUSTER table caused a memory leak in
        the NDB subscription manager (SUMA) which could lead to mysqld hanging,
        due to the fact that the resource shortage was not reported back to the
        NDB kernel correctly.

[12 Dec 2008 23:29] Bugs System

Pushed into 6.0.7-alpha  (revid:[e-mail]-20080918142925-8h6oh88zgk2u7as0) (version source revid:[e-mail]-20080925105539-wd6gbofp5alv9j93) (pib:5)