docs: add MySQL 8.4 migration guide for customers - #10163
Conversation
Customer-facing guide covering how to enable MySQL 8.4 via pantheon.yml, pre-migration checklist, CMS compatibility matrix, reserved word conflicts, migration process and timing, common post-migration issues (ONLY_FULL_GROUP_BY, collation mismatches), and limitations. Refs: PRT-3742
|
Successfully created multidev environment: pr-10163 |
rachelwhitton
added
Type: New Content
|
Successfully created multidev environment: pr-10163 |
|
|
||
| - **No self-service rollback.** Reverting from MySQL 8.4 to MariaDB requires Pantheon support. Always test on a [Multidev](/guides/multidev) first. | ||
| - **Backups are engine-specific.** A backup taken on MySQL 8.4 cannot be restored to a MariaDB environment, and vice versa. | ||
| - **MariaDB 10.6 required.** Your site must be on MariaDB 10.6 before migrating to MySQL 8.4. Sites on older MariaDB versions will be upgraded to 10.6 first automatically. |
There was a problem hiding this comment.
@kanishkaverma in Slack we discussed making this a recommendation rather than a requirement. Let's hold off on publishing until we know for certain.
There was a problem hiding this comment.
Softened to "recommended" with a note that the migration currently requires 10.6 as the source version. That way the doc is accurate to today's behavior but doesn't read as a hard prerequisite for customers planning ahead.
| |-----|----------------|-------| | ||
| | WordPress 6.x | All versions | Fully compatible | | ||
| | WordPress 5.x | 5.9+ | Older versions may hit reserved word or sql_mode issues | | ||
| | Drupal 10 | 10.2+ | Earlier versions may need patches for the `GROUPS` reserved word | |
There was a problem hiding this comment.
What patches would they need? It might be wiser for us to just recommend upgrading to the highest available point release.
There was a problem hiding this comment.
Good call. Changed both WordPress 5.x and Drupal 10 to recommend upgrading to the latest point release rather than pinning specific versions.
| Before enabling MySQL 8.4, consider the following limitations: | ||
|
|
||
| - **No self-service rollback.** Reverting from MySQL 8.4 to MariaDB requires Pantheon support. Always test on a [Multidev](/guides/multidev) first. | ||
| - **Backups are engine-specific.** A backup taken on MySQL 8.4 cannot be restored to a MariaDB environment, and vice versa. |
There was a problem hiding this comment.
Why can't a backup taken in MariaDB be imported to a MySQL environment? aren't we doing this conversion with a backup and import?
There was a problem hiding this comment.
You are right that the migration itself uses backup and import internally, and the platform handles the engine conversion during that process. The limitation is that a manual backup/restore initiated by the customer does not do that conversion. Rewrote the bullet to explain both sides.
Co-authored-by: Steve Persch <stevector@users.noreply.github.com>
Co-authored-by: Steve Persch <stevector@users.noreply.github.com>
|
Successfully created multidev environment: pr-10163 |
1 similar comment
|
Successfully created multidev environment: pr-10163 |
|
There doesn't seem to be a way to track progress via workflows, at least for multidev environments. The typical "Synced code on ..." workflow will be logged, but it completes nearly instantaneously. Meanwhile, the database migration is happening in the background. The only way that I know it's happening is because I'm periodically running |
…stream rollout note - Backups bullet: explain that the platform handles conversion during migration, but manual backup/restore does not cross engines. - MariaDB 10.6: soften from 'required' to 'recommended' per Slack discussion, while noting the migration currently requires it. - CMS table: replace specific version pins with 'latest point release' recommendation per stevector feedback. - Add upstream rollout note explaining managed upstream vs custom upstream behavior for pantheon.upstream.yml changes.
|
Successfully created multidev environment: pr-10163 |
4 participants
Adds a new page to the MariaDB and MySQL guide covering MySQL 8.4 migration.
Content
Context
MySQL 8.4 LTS support is nearing GA. This guide is part of pre-release prep for PS/CS/TS readiness (PRT-3742). Based on at-scale validation of 14 sites from 0 MB to 85 GB (PRT-3727).
The pantheon.yml page will also need an update to mention MySQL 8.4 alongside MariaDB versions, but that can be a follow-up.
Refs: PRT-3742