MySQL 8.0 End of Support Countdown: What Issues Will You Face When Upgrading?
MySQL 8.0 End of Maintenance — Upgrade Guidance
Starting April 2026, MySQL 8.0 will reach end of maintenance, meaning:
- No more patch updates, bug fixes, or security vulnerability repairs from Oracle.
- Bug reports filed after this date will likely receive no response.
- Deprecated features will be removed — not just marked with warnings.
Recommended Actions
- Upgrade to MySQL 8.4 LTS as soon as possible.
- Replace legacy tools — for example, move from the `mysql` CLI to MySQL Shell (`mysqlsh`).
- Update removed commands, such as `SET PASSWORD = PASSWORD(...)`.
- Prepare for system variable changes and new defaults.
- Review application and tool compatibility, especially for:
- Changed or removed system variables.
- Monitoring and analytics integrations.
- Self-developed or open-source database tools.
---
MySQL 8.0 → 8.4 Key Changes
1. Removed System Variables and Features
| Category | Removed Variable / Feature | Description | Replacement / Solution |
|------------------------|----------------------------------------|---------------------------------------------------------|------------------------|
| Transaction | `tx_isolation` | Old transaction isolation variable name | Use `transaction_isolation` |
| Transaction | `tx_read_only` | Old read-only mode variable name | Use `transaction_read_only` |
| Binary Logs | `expire_logs_days` | Binlog expiration (days) | Use `binlog_expire_logs_seconds` (`7 days` = `604800 seconds`) |
| Semi-sync Replication | (more examples omitted) | — | — |
---
Semi-Synchronous Replication Changes
- `rpl_semi_sync_master_wait_for_slave_count` → `rpl_semi_sync_source_wait_for_replica_count`
- `rpl_semi_sync_master_timeout` → `rpl_semi_sync_source_timeout`
- `rpl_semi_sync_master_trace_level` → `rpl_semi_sync_source_trace_level`
- `rpl_semi_sync_slave_trace_level` → `rpl_semi_sync_replica_trace_level`
---
Group Replication
- `group_replication_ip_whitelist` → `group_replication_ip_allowlist`
---
Networking
- `skip_name_resolve`
- Old: accepts ON/OFF
- New: accepts numeric `0` or `1`
---
Functions
- `PASSWORD()` — Removed
- Use:
CREATE USER ... IDENTIFIED BY '...';
ALTER USER ... IDENTIFIED BY '...';---
Replication Commands
- Old: `CHANGE MASTER TO`, `START SLAVE`, `SHOW SLAVE STATUS`
- New: `CHANGE REPLICATION SOURCE TO`, `START REPLICA`, `SHOW REPLICA STATUS`
---
2. Deprecated System Variables and Features
| Category | Deprecated Variable / Feature | Description | Replacement / Recommendation |
|----------------|--------------------------------|-------------------------------------------------|------------------------------|
| Authentication | `mysql_native_password` | Weak plugin | Migrate to `caching_sha2_password` |
| Authentication | `default_authentication_plugin`| Sets default plugin | Renamed to `default_authentication_policy` |
| Command | `FLUSH HOSTS` | Clears host cache | Remove from scripts if unused |
| Startup Option | `--skip-grant-tables` | Disables privilege checks (security risk) | Use `--init-file` for password recovery |
| Data Type | `FLOAT(M,D)`, `DOUBLE(M,D)` | Non-standard precision syntax | Use standard `FLOAT` / `DOUBLE` |
---
Potentially Removed or Deprecated Parameters (Verify Before Migration)
Potentially Removed
- `--log_slow_verbosity` — Logging options streamlined in 8.4.
- `stored_program_cache_size` — Deprecated in 8.0, likely removed in 8.4.
Potentially Deprecated
- `query_cache_size`, `query_cache_type` — Deprecated since 8.0; check for usage.
- `innodb_old_blocks_time` — Possible deprecation warning in new release.
- `innodb_print_all_deadlocks` — Verify if new diagnostics replace it.
---
High Version Adoption Challenges
With fewer deployments using MySQL >8.0:
- Documentation and community support may be scarce.
- Extra planning required for:
- Backups
- High availability
- Performance tuning
- Migration testing
> Tip: Share upgrade experiences to help the broader DBA and developer community.
---
Leveraging AI Tools for Upgrade Documentation
Platforms like AiToEarn官网 provide:
- AI-powered content generation
- Cross-platform publishing (Douyin, Kwai, WeChat, Bilibili, Rednote, Facebook, Instagram, LinkedIn, Threads, YouTube, Pinterest, X)
- Analytics & AI模型排名
- Open-source ecosystem for monetizing technical expertise
This enables teams to maintain clear, updated MySQL migration guides and share them widely.
---
Source: AustinDatabases (ID: AustinDatabases)
📧 dbaplus community welcomes submissions: editor@dbaplus.cn