Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Modified the SST process to run mysql_upgrade

Description

Currently we using the following instructions to upgrade from PXC version <=5.7.18 to 5.7.19

We may be able to accomplish the same thing using:

Using mysql_upgrade -s on an on-line node should only update the system tables.   However,  there may a lot of DDL commands transferred that may cause issues with some cluster configurations.   Please log all of the traffic on a node during mysql_ugprade -s and determine if this is a safe alternative to a manual schema update.

Environment

None

Smart Checklist

Activity

Show:

Ramesh Sivaraman February 12, 2019 at 1:44 AM

okay sure.

roel.vandepaar February 12, 2019 at 12:34 AM

this will need extensive testing.

KennT February 11, 2019 at 11:54 AM

commit 745c1d67e5e006f05de5b4d0687ec8420fdf7c91
Author: Kenn Takara <kenn.takara@percona.com>
Date: Mon Feb 11 00:27:54 2019 -1000

: run mysql_upgrade as part of SST

Now running mysql_upgrade as part of the SST. This makes it easier
to upgrade (since the donor would be a lower version and the joiner
would be a higher version).

c

roel.vandepaar January 30, 2018 at 7:02 AM

Some updates on some points above

A new DOC ticket will be logged for this. Excluding the '-s'.

This is not applicable anymore, mysql_upgrade already now executes the same SQL, internally.

So this will be logged in the new DOC ticket, along with the clear instructions to run SST on every upgrade (a shortcoming that was found) AND to try and upgrade a whole cluster/different nodes in as close a succession as possible to avoid a problem where a node gets a full SST (instead of an IST) from an older version (i.e. full data dir, leading to problems) after it had been upgraded locally/had mysql_upgrade run already.

Open to further discussion.

roel.vandepaar January 23, 2018 at 8:49 PM
Edited

Given the points above, I propose we close this ticket and instead create a new ticket for only the "include pxc_cluster_view.sql inside mysql_upgrade" proposed change in a minor release.

For "mysql_upgrade auto-execution during SST" I propose we create another ticket and set it for 8.0 implementation.

This makes both items much more outlined, defined, and - importantly - testable and secure (i.e. we can more or less assure that our testing can accurately cover these individual items).

Done

Details

Assignee

Reporter

Time tracking

2w 2d 12m logged

Fix versions

Affects versions

Due date

Priority

Smart Checklist

Created September 25, 2017 at 7:24 PM
Updated March 6, 2024 at 10:21 PM
Resolved February 11, 2019 at 11:54 AM