Re: Mysql community edition upgrade from 8.0.36 to 8.4 (LTS)
Hello Raja,
Yes, 8.0.36 -> 8.4 is a supported direct in-place upgrade, you don't need to stop at an intermediate 8.0.x version first since 8.4 is the next LTS after the 8.0 series and MySQL supports upgrading from any 8.0.x to 8.4 directly.
A few things worth doing before you touch production:
Run MySQL Shell's upgrade checker first: util.checkForServerUpgrade(). This flags deprecated features, syntax, and config options that'll break on 8.4 before you actually upgrade, saves a lot of surprises.
Check sql_mode and any use of deprecated features, MySQL 8.4 removes a few things that were only deprecated in 8.0, like mysql_native_password no longer being enabled by default (it's still available but disabled unless you explicitly turn it on), so if Axway B2Bi or any tooling connects using native password auth, that's the first thing to check.
Review your replication setup if you have any, GTID-based replication behavior and some replication-related variables changed defaults between 8.0 and 8.4.
Back up before starting, obviously, but also take an mysqldump --all-databases or snapshot at the EC2/EBS level so rollback is fast if something's off, in-place upgrades aren't easily reversible.
On EC2, do the upgrade on a cloned/staging instance first if at all possible, restore a recent snapshot to a test instance, run the upgrade there, and validate the app layer against it before touching prod.
For the deprecated/removed features list specifically, the official upgrade notes are the most reliable source since they change per release, worth checking those directly rather than relying on secondhand advice for the exact list relevant to your setup.
Regards,
Herrick Peterson
DevOps Engineer
Accuweb.cloud