Databases & NoSQL

MySQL Version Lock Policy for Production Stability

Published · Updated 2 min read
Knowledge base article
Contents (9 sections)

Purpose: To ensure MySQL service stability across all servers by locking the MySQL version at 8.0.37 due to known issues in subsequent releases. This policy outlines the rationale, implementation steps, and review schedule for version-locking MySQL packages.


Packages Covered Under Lock

  • mysql-community-server

  • mysql-community-client

  • mysql-community-common

  • mysql-community-libs

  • mysql-community-devel

  • mysql-community-client-plugins

  • mysql-community-icu-data-files

  • mysql80-community-release


Rationale for Locking at 8.0.37

  • MySQL versions 8.0.38 and above have critical issues, including:

    • mysqld crashes when restarting with a large number of tables.

    • performance_schema inconsistencies and memory issues.

    • replication instabilities reported by multiple users.

  • These bugs are publicly acknowledged on community forums and have not yet been fully addressed by Oracle.

  • Source references:


Implementation Steps

1. Confirm Installed Version

code
rpm -q mysql-community-server

Expected:

code
mysql-community-server-8.0.37-1.el8

2. Install Version Lock Plugin (if not present)

code
dnf install python3-dnf-plugin-versionlock -y
code
dnf versionlock add mysql-community-server-8.0.37*
dnf versionlock add mysql-community-client-8.0.37*
dnf versionlock add mysql-community-common-8.0.37*
dnf versionlock add mysql-community-libs-8.0.37*
dnf versionlock add mysql-community-devel-8.0.37*
dnf versionlock add mysql-community-client-plugins-8.0.37*
dnf versionlock add mysql-community-icu-data-files-8.0.37*
dnf versionlock add mysql80-community-release-8.0.37*

4. Confirm Lock

code
dnf versionlock list | grep mysql

Review Schedule

Frequency: Every 3 months (Quarterly)

Next Review Due: [Auto-fill next quarter date based on current quarter]

Review Tasks:

  • Check MySQL official release notes.

  • Monitor vendor bug tracker / forums for fixes.

  • Validate newer versions in staging before unlocking.


Unlock Procedure (Once Safe Version is Confirmed)

code
dnf versionlock delete mysql-community-server
# repeat for each package as needed

dnf update mysql-community-server

Maintainer Note: This lock policy is critical for stability of multi-tenant hosting environments and should not be bypassed without change control approval.

Responsible Team: Linux Server Administration Contact: [email protected]

Was this article helpful?

Your answer helps us decide what to improve next.

Still need help? Open a support ticket and our team will reply.

Prefer an app? Add this site to your home screen.Get the app
MySQL Version Lock Policy for Production Stability - Knowledge Base