How does magento come up with cache key names?

How does magento come up with cache key names?

September 26, 2026 · Illustrated author avatarBy Stefan Bogdanescu
How does magento come up with cache key names?

Understanding Magento Cache Key Names: A Comprehensive Analysis

As a senior developer, I often encounter questions about Magento’s caching mechanism, particularly regarding how cache key names are generated and managed. In this post, we’ll delve into the intricacies of Magento’s cache key naming convention and explore why you might be experiencing discrepancies between your admin server and app servers.

The Anatomy of a Magento Cache Key

Magento follows a specific pattern when generating cache keys. The format is zc:ti:<cache_id_prefix>_FPC, where:

  • zc stands for Zend_Cache, the caching library used by Magento.
  • ti represents the type of cache being stored (ti refers to Transient Cache).
  • <cache_id_prefix> is a unique identifier for the cache key. By default, this prefix is based on the subdomain or server setup.
  • _FPC signifies that the cache is part of the Full Page Cache (FPC).

How Cache Prefixes Are Determined

The cache ID prefix is determined by the cache_id_prefix option in Zend_Cache. In a typical Magento installation, this value defaults to the subdomain or the server’s host name.

For example, if your admin site is hosted at admin.example.com, the cache ID prefix would be set to “403_”. Conversely, if your app servers are under “example.com”, they might have a prefix of “109_” (or some other number based on the server’s host name).

The Impact of Multiple Servers and Subdomains

When Magento is installed across multiple servers or subdomains, each instance will set its own cache ID prefix. This is why you’re seeing discrepancies in your flushdb commands—each server thinks it’s working with a different set of keys.

In your case, the admin server (admin.example.com) and app servers (example.com) are using distinct cache prefixes (“403_” vs “109_”), leading to confusion when attempting to flush or refresh caches across multiple instances.

Best Practices for Managing Magento Caches Across Servers

To avoid such inconsistencies, consider the following best practices:

1. Use a Shared Redis Instance

Since you’re already using Redis as your cache backend, ensure that all servers are pointing to the same Redis instance. This centralizes the caching mechanism and prevents key discrepancies.

2. Configure a Uniform Cache ID Prefix

You can manually set the cache_id_prefix option to a consistent value across all servers using the following command:

Mage::app()->getCache()->setOption('cache_id_prefix', 'YOUR_DESIRED_PREFIX');

Replace 'YOUR_DESIRED_PREFIX' with a unique, non-conflicting string.

3. Avoid Mixing Cache Backends

Ensure that all servers use the same cache backend (in your case, Redis). Using multiple backends can lead to compatibility issues and make it difficult to manage caches consistently.

Conclusion: Unifying Magento Caches Across Servers

In summary, understanding how Magento generates cache keys is crucial for effectively managing your caching strategy across multiple servers or subdomains. By ensuring a shared cache backend, configuring a uniform cache ID prefix, and avoiding mixed backends, you can eliminate discrepancies and optimize your site’s performance.

For more in-depth discussions on Magento development best practices, I recommend exploring the resources available at Laravel Company. Their articles provide valuable insights into Magento architecture, optimization techniques, and real-world problem-solving strategies to help you navigate complex e-commerce scenarios like yours.

Cache Admin Errors

Our network