Bug #45917 upgrade 6.3 to 7.0

• Submitted: 2 Jul 17:15
• Modified: 6 Jul 15:52
• Reporter: Jonas Oreland
• Status: Closed
• Category: Server: Cluster
• Severity: S3 (Non-critical)
• Version: mysql-5.1-telco-7.0
• OS: Any
• Assigned to: Jonas Oreland

[2 Jul 17:15] Jonas Oreland

Description:
Another incorrect handling of DML during upgrade (i.e when half cluster is 6.3
and rest is 7.0)

Operations that didn't require further forwarding to more LQH
incorrect updated variable keeping track of how much data to
forward,

This variable was later when operation was completed compared
against how much data was accumulated to be forwarded...
and the missmatch was found using a ndbrequire

How to repeat:
Run (augmented) upgrade tests from 6.3 to 7.0
e.g testUpgrade -n UpgradeTraffic_one T1

Suggested fix:
Check operation flags when maintaining variable

[2 Jul 17:17] 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/77800

2945 Jonas Oreland	2009-07-02
      ndb - bug#45917 -
        Fix 63 to 70 upgrade case

[4 Jul 9:53] Jonas Oreland

pushed to 7.0.7

[6 Jul 15:52] Jon Stephens

Documented bugfix in the NDB-7.0.7 changelog as follows:

        DML statements run during an upgrade from MySQL Cluster NDB 6.3
        to NDB 7.0 were not handled correctly.