Bug #61498 Mixed upgrade broken for mysqld
Submitted: 13 Jun 2011 10:16 Modified: 13 Jun 2011 13:33
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.20 OS:Any
Assigned to: Jonas Oreland CPU Architecture:Any

[13 Jun 2011 10:16] Jonas Oreland 
Description:
Introduced by bug#57164, (re)starting a mysqld while having mixed version
causes mysqld to remain in read-only mode, until all data-nodes have been
upgraded.

How to repeat:
restart mysqld when having upgraded e.g half of the data-nodes.
observe that it stays in read-only mode

Suggested fix:
.
[13 Jun 2011 10:51] Jonas Oreland 
pushed to 7.0.26 and 7.1.15
[13 Jun 2011 13:33] Jon Stephens 
Documented fix in the NDB 7.0.26 and 7.1.15 changelogs as follows:

        Restarting a mysqld during a rolling upgrade with data nodes
        running a mix of old and new versions caused the mysqld to run
        in read-only mode.

Closed.