Bug #44827 Upgrade from 6.3 to 7.0 with traffic ongoing

Submitted:	12 May 2009 14:51	Modified:	14 May 2009 13:45
Reporter:	Jonas Oreland	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S3 (Non-critical)
Version:	7.0	OS:	Any
Assigned to:	Jonas Oreland	CPU Architecture:	Any

Description:
1) When performing an online upgrade between 6.3 and 7.0
7.0 will crash for some tables due to incorrect key-len being sent
during node-recovery (copy phase). This is how 6.3 works, but 7.0
has not been coded to handle it.

2) In 7.0 the handling of triggers for UNIQUE indexes has changed compared
   to 6.3. The code did not correctly handle the old-format
   causing other random transaction aborts with error 208 (internal error)
   or node crash as consequence.

How to repeat:
testUpgrade -n Upgrade_Traffic

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/73834

2889 Jonas Oreland	2009-05-12
      ndb - bug#44827 - Fix upgrade 6.3 to 7.0 with traffic
        1) keylen in NR
        2) unique index trigger handling

Pushed into 5.1.34-ndb-7.0.6 (revid:jonas@mysql.com-20090512150511-7jab71u8g1yhm1y4) (version source revid:jonas@mysql.com-20090512150140-mfjyf10mbvet8v8g) (merge vers: 5.1.34-ndb-7.0.6) (pib:6)

Pushed into 5.1.34-ndb-7.0.6 (revid:jonas@mysql.com-20090512184056-fqn5bzk09p47x84h) (version source revid:jonas@mysql.com-20090512184056-fqn5bzk09p47x84h) (merge vers: 5.1.34-ndb-7.0.6) (pib:6)

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/73867

2891 Jonas Oreland	2009-05-12
      ndb - bug#44827, fix bug in bugfix causing ndbmtd to crash

Documented bugfix in the NDB-7.0.6 changelog as follows:

        Online upgrades to MySQL Cluster NDB 7.0 from a MySQL Cluster NDB 6.3
        release could fail due to changes in the handling of key lengths
        and unique indexes during node recovery.

Page generated in 0.041 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.