Home / Database / MySQL Query Cache Deprecated Issues

Database

MySQL Query Cache Deprecated Issues

MySQL query cache issues when deprecated feature still enabled in MySQL 8.0.

Published: Jan 23, 20269 min readBy FixWikiHub Editorial Team

Abstract illustration for a troubleshooting knowledge base category.

Introduction

The MySQL query cache was a feature that cached the result sets of identical SELECT statements, allowing subsequent identical queries to be served from memory rather than re-executing against the database. While this sounded beneficial, the query cache had significant limitations: it only helped with read-heavy workloads on static data, it introduced locking contention on write-heavy systems, and it became increasingly problematic as data sets grew.

In MySQL 5.7, the query cache was deprecated, and in MySQL 8.0, it was completely removed. Many applications and configurations still reference query cache settings (query_cache_type, query_cache_size, query_cache_limit), which now cause errors or warnings during MySQL startup or when upgrading from earlier versions. Understanding how to properly remove these settings and implement alternative caching strategies is essential for a smooth MySQL 8.0 migration.

The removal of the query cache was a deliberate design decision by the MySQL team. Modern workloads and hardware have evolved, and the query cache's architectural limitations outweighed its benefits for most use cases. The single mutex protecting the query cache became a bottleneck on multi-core systems, and the overhead of invalidating cache entries on every write operation was significant.

Symptoms

When upgrading to MySQL 8.0 with query cache configuration still present, you will encounter these symptoms:

MySQL server fails to start with "unknown variable" errors
Error messages in MySQL error log: unknown variable 'query_cache_type=1' or unknown variable 'query_cache_size=64M'
Warnings about deprecated options during configuration validation
Applications that relied on query cache behavior may show performance changes
MySQL configuration validation tools report errors for query cache settings
Configuration management tools fail when applying existing MySQL templates
SHOW VARIABLES LIKE 'query_cache%'; returns empty results in MySQL 8.0

Common error messages in MySQL logs:

bash

[ERROR] unknown variable 'query_cache_type=1'
[ERROR] unknown variable 'query_cache_size=64M'
[ERROR] unknown variable 'query_cache_limit=2M'
[ERROR] Aborting

Or with mysqld --validate-config:

bash

mysqld: [ERROR] Found unknown option '--query-cache-type=1' in configuration file.

Common Causes

Several factors contribute to MySQL query cache deprecation issues:

1.Inherited configuration files: Configuration files from MySQL 5.7 or earlier versions that contain query_cache_* settings are incompatible with MySQL 8.0.
2.Third-party configuration templates: Many database configuration generators and templates still include query cache settings by default, not accounting for MySQL 8.0 changes.
3.Monitoring and tooling expectations: Some monitoring tools and scripts check for query cache metrics that no longer exist in MySQL 8.0, causing alerts or errors.
4.Documentation lag: Some guides and tutorials still recommend query cache settings for performance tuning, leading to confusion.
5.Configuration management drift: Puppet, Chef, Ansible, or other configuration management tools may still apply query cache settings from older module versions.
6.Application-level expectations: Applications might check for query cache status or attempt to enable/disable it programmatically.
7.Backup restoration: Restoring MySQL 5.7 configuration backups onto MySQL 8.0 servers introduces incompatible settings.

Step-by-Step Fix

Follow these steps to resolve MySQL query cache deprecation issues:

Step 1: Identify all query cache configuration references

Search for query cache settings across all configuration locations:

```bash # Check main MySQL configuration grep -r "query_cache" /etc/mysql/

# Check additional configuration directories grep -r "query_cache" /etc/my.cnf* 2>/dev/null grep -r "query_cache" /usr/etc/my.cnf* 2>/dev/null

# Check for command-line options in systemd service systemctl cat mysql 2>/dev/null | grep -i query_cache systemctl cat mysqld 2>/dev/null | grep -i query_cache

# Check for environment variable configurations grep -r "query_cache" /etc/default/mysql* 2>/dev/null grep -r "query_cache" /etc/sysconfig/mysql* 2>/dev/null ```

Step 2: Remove query cache settings from configuration files

Edit configuration files to remove or comment out query cache settings:

```bash # Backup current configuration sudo cp /etc/mysql/my.cnf /etc/mysql/my.cnf.backup

# Edit the configuration file sudo nano /etc/mysql/my.cnf ```

Remove or comment out these lines:

ini

# Comment out or remove these deprecated settings:
# query_cache_type = 1
# query_cache_size = 64M
# query_cache_limit = 2M
# query_cache_min_res_unit = 4K
# query_cache_wlock_invalidate = OFF

Alternatively, use sed to remove them automatically:

bash

# Remove query cache settings from all MySQL config files
sudo sed -i '/query_cache/d' /etc/mysql/my.cnf
sudo sed -i '/query_cache/d' /etc/mysql/mysql.conf.d/*.cnf
sudo sed -i '/query_cache/d' /etc/mysql/conf.d/*.cnf

Step 3: Validate configuration before restarting

Always validate configuration before applying changes:

```bash # Validate configuration file syntax (MySQL 8.0+) mysqld --validate-config

# Or use this for earlier validation mysqld --help --verbose 2>&1 | grep -i error

# Check for any remaining unknown variables mysqld --print-defaults | grep -i query_cache ```

Step 4: Update configuration management tools

If using configuration management, update your playbooks/manifests:

For Ansible:

yaml

# Remove from templates
- name: Configure MySQL (MySQL 8.0 compatible)
  template:
    src: my.cnf.j2
    dest: /etc/mysql/my.cnf
  when: mysql_version is version('8.0', '>=')
  # Remove query_cache settings from my.cnf.j2 template

For Puppet:

puppet

# Remove query_cache_* parameters from mysql::server class
class { 'mysql::server':
  # Do NOT include these for MySQL 8.0:
  # query_cache_type => '1',
  # query_cache_size => '64M',
  override_options => {
    'mysqld' => {
      # MySQL 8.0 compatible options only
      'max_connections' => '200',
      'innodb_buffer_pool_size' => '1G',
    }
  }
}

Step 5: Update monitoring and alerting

Remove checks for query cache metrics:

```sql -- This query returns empty in MySQL 8.0 SHOW STATUS LIKE 'Qcache%';

-- Instead, monitor these alternatives: SHOW STATUS LIKE 'Innodb_buffer_pool%'; SHOW STATUS LIKE 'Handler%'; SHOW STATUS LIKE 'Select%'; ```

Update monitoring scripts:

```bash # Old (MySQL 5.7) monitoring check - remove this # mysql -e "SHOW STATUS LIKE 'Qcache_hits'"

# New (MySQL 8.0) buffer pool monitoring mysql -e "SHOW STATUS LIKE 'Innodb_buffer_pool_read%'" ```

Step 6: Restart MySQL service

After configuration changes, restart MySQL:

```bash # Stop MySQL sudo systemctl stop mysql

# Start MySQL with validated configuration sudo systemctl start mysql

# Verify MySQL is running sudo systemctl status mysql

# Check error log for any issues sudo tail -f /var/log/mysql/error.log ```

Step 7: Verify query cache removal

Confirm query cache settings are gone:

```sql -- This should return empty result in MySQL 8.0 SHOW VARIABLES LIKE 'query_cache%';

-- Check MySQL version SELECT VERSION();

-- Verify server is running properly SHOW STATUS LIKE 'Uptime'; ```

Alternative Caching Strategies

Since MySQL 8.0 removed the query cache, implement these alternatives:

Option 1: Increase InnoDB Buffer Pool

ini

[mysqld]
# Allocate 70-80% of available RAM for InnoDB buffer pool
innodb_buffer_pool_size = 4G
innodb_buffer_pool_instances = 4

Option 2: Application-level caching

Implement caching in your application layer:

```python # Using Redis for query result caching import redis import json

cache = redis.Redis(host='localhost', port=6379, db=0)

def get_user(user_id): cache_key = f"user:{user_id}" cached = cache.get(cache_key)

if cached: return json.loads(cached)

# Query database result = db.execute(f"SELECT * FROM users WHERE id = {user_id}")

# Cache for 5 minutes cache.setex(cache_key, 300, json.dumps(result)) return result ```

Option 3: MySQL memcached plugin

```sql -- Install memcached plugin for InnoDB (if available) INSTALL PLUGIN daemon_memcached SONAME 'libmemcached.so';

-- Create container table CREATE TABLE test.memcached_test ( id VARCHAR(32) NOT NULL, value VARCHAR(1024) NOT NULL, PRIMARY KEY (id) ) ENGINE=InnoDB; ```

Verification

After removing query cache settings and implementing alternatives:

```bash # Verify MySQL is running without errors sudo systemctl status mysql

# Check error log for startup success sudo grep -i "ready for connections" /var/log/mysql/error.log

# Monitor buffer pool hit rate mysql -e "SHOW STATUS LIKE 'Innodb_buffer_pool_read%';" | \ awk 'NR>1 {reads+=$2} END {print "Buffer pool hit rate:", reads}'

# Check for any remaining configuration warnings mysqld --validate-config && echo "Configuration valid" ```

Prevention

To prevent query cache issues in future MySQL environments:

1.Version-aware configuration management: Use conditional logic in configuration management tools to apply different settings based on MySQL version.
2.Configuration testing in CI: Include MySQL configuration validation in your CI/CD pipeline before deploying to production.
3.Keep documentation updated: Maintain version-specific documentation for MySQL configuration, clearly marking deprecated options.
4.Use official MySQL Docker images: When containerizing, use official MySQL 8.0 images that don't include query cache settings.
5.Monitor deprecation notices: Watch MySQL release notes for deprecated features to prepare for future removals.
6.Implement external caching early: Don't rely on built-in query cache. Implement Redis, Memcached, or application-level caching as part of your architecture.

[Database troubleshooting: Fix Backup Exclusive Lock Table Production Writes ](backup-exclusive-lock-table-production-writes)
[Fix Connection Pool Leak Application Not Closing Issue in Database](connection-pool-leak-application-not-closing)
[Fix Connection Reset Idle Timeout Firewall Issue in Database](connection-reset-idle-timeout-firewall)
[Fix Connection Reset Idle Timeout Serverless Database Issue in Database](connection-reset-idle-timeout-serverless-database)
[Fix Connection String Encoding Special Characters Issue in Database](connection-string-encoding-special-characters)

Was this guide helpful?

Related search paths

People also search for

If the symptom is close but not identical, these search paths usually surface the right neighboring fixes faster than scrolling the full archive.

MySQL Query Cache Deprecated Issues MySQL Query Cache Deprecated Issues Database MySQL Query Cache Deprecated Issues troubleshooting MySQL Query Cache Deprecated Issues fix MySQL query cache issues when deprecated feature still enabled in MySQL 8 Database MySQL query cache issues when deprecated feature still enabled in MySQL 8

Explore Related Topics

Browse Guides from Other Categories

Discover troubleshooting guides from related categories to expand your knowledge.

FAQ

Database Troubleshooting FAQs

Common questions about troubleshooting and preventing similar issues

How do I know if this database-errors troubleshooting guide applies to my situation?

This guide is designed for database-errors issues. If you're experiencing similar symptoms described in the article, follow the step-by-step instructions. Start with the most common causes and work through the diagnostic process.

Is it safe to follow these database-errors troubleshooting steps?

Yes, all steps are designed to be safe and non-destructive. We recommend creating backups before making significant changes and testing each step before proceeding to the next.

How long does it typically take to resolve this type of database-errors issue?

Most database-errors issues can be resolved within 30 minutes to 2 hours, depending on the complexity and root cause. Follow the troubleshooting flow to identify and fix the problem efficiently.

How can I prevent this database-errors issue from happening again?

Regular maintenance, monitoring, and following best practices for database-errors configuration can help prevent recurrence. Consider implementing automated checks and alerts for early detection.

Written by

FixWikiHub Editorial Team

Our editorial team consists of experienced DevOps engineers, systems administrators, and cloud architects with hands-on experience in production environments across AWS, Azure, GCP, and on-premises infrastructure.

Every guide undergoes technical review for accuracy and is updated when software versions, commands, or best practices change.

Last updated: Jan 23, 2026

About our team

Important Notice

Disclaimer & Safety Guidelines

The troubleshooting steps in this guide are provided for educational and informational purposes. Before applying any changes to production systems:

Test in a staging environment first — Always verify commands and configurations in a non-production environment before deploying to live systems.
Create backups — Ensure you have current backups of databases, configurations, and critical files before making changes.
Understand the impact — Review how each step may affect your specific environment, dependencies, and users.
Consult official documentation — This guide supplements, but does not replace, official vendor documentation and best practices.

FixWikiHub is not responsible for any damages arising from the use of this content. See our Terms of Use for more information.

Resources

Official Documentation & Further Reading

For authoritative information, consult the official documentation for the technologies discussed in this guide. Our troubleshooting content supplements, but does not replace, vendor documentation.

AWS Documentation — Official Amazon Web Services guides and API references
Kubernetes Documentation — Official Kubernetes documentation
Nginx Documentation — Official Nginx web server documentation
Apache Documentation — Official Apache HTTP Server documentation
Docker Documentation — Official Docker container documentation

MySQL Query Cache Deprecated Issues

Introduction

Symptoms

Common Causes

Step-by-Step Fix

Step 1: Identify all query cache configuration references

Step 2: Remove query cache settings from configuration files

Step 3: Validate configuration before restarting

Step 4: Update configuration management tools

Step 5: Update monitoring and alerting

Step 6: Restart MySQL service

Step 7: Verify query cache removal

Alternative Caching Strategies

Option 1: Increase InnoDB Buffer Pool

Option 2: Application-level caching

Option 3: MySQL memcached plugin

Verification

Prevention

People also search for

Browse Guides from Other Categories

WordPress

SSL

DNS

Database Troubleshooting FAQs

FixWikiHub Editorial Team

Disclaimer & Safety Guidelines

Official Documentation & Further Reading

MySQL Query Cache Deprecated Issues

Introduction

Symptoms

Common Causes

Step-by-Step Fix

Step 1: Identify all query cache configuration references

Step 2: Remove query cache settings from configuration files

Step 3: Validate configuration before restarting

Step 4: Update configuration management tools

Step 5: Update monitoring and alerting

Step 6: Restart MySQL service

Step 7: Verify query cache removal

Alternative Caching Strategies

Option 1: Increase InnoDB Buffer Pool

Option 2: Application-level caching

Option 3: MySQL memcached plugin

Verification

Prevention

Related Articles

People also search for

Share this guide

More Database Troubleshooting Guides

Browse Guides from Other Categories

Database Troubleshooting FAQs

FixWikiHub Editorial Team

Disclaimer & Safety Guidelines

Official Documentation & Further Reading