Magento How to disable Redis Caching at run time if REDIS server failover

Magento How to disable Redis Caching at run time if REDIS server failover

September 27, 2026 · Illustrated author avatarBy Stefan Bogdanescu
Magento How to disable Redis Caching at run time if REDIS server failover

Handling Redis Failover for Magento Caching

When dealing with an unexpected Redis outage like you experienced, it’s crucial to have a fallback mechanism in place to ensure your Magento store remains operational. Here are the best options to handle such scenarios effectively.

Understanding the Problem

The error message Can't save in background: fork: Cannot allocate memory typically indicates that Redis has run out of available memory or is facing high load, causing it to fail when trying to process new requests. In your case, Magento was configured to use Redis for caching and session storage.

Enabling the Fallback to Disk File Cache

To ensure your store doesn’t go down during a Redis failure, you can configure Magento to automatically switch to disk file cache when Redis is unavailable. Here’s how to achieve this:

  1. Modify the local.xml configuration

    Open your app/etc/local.xml file and update the <cache> section as follows:

    <cache>
      <backend>Cm_Cache_Backend_Redis</backend>
      <backend_options>
        <!-- Your Redis server details -->
        <server>127.0.0.1</server>
        <port>6379</port>
        <!-- ... other options ... -->
    
        <!-- Add these lines for fallback to disk file cache -->
        <fallback>Cm_Cache_Backend_File</fallback>
        <fallback_options><cache_dir>/var/cache/</cache_dir></fallback_options>
    
      </backend_options>
    </cache>
    

    The new <fallback> and <fallback_options> elements tell Magento to use the Cm_Cache_Backend_File (disk file cache) if Redis isn’t available.

  2. Clear the cache

    After updating the configuration, run the following command in your terminal to clear the current cache:

    php -f maintenance/clear_cache.php
    

    This will force Magento to re-cache everything using the new fallback mechanism.

Monitoring and Recovery

Once you’ve implemented this change, here are some additional best practices to follow:

  • Monitor Redis health: Use tools like redis-cli or monitoring services (e.g., Prometheus + Grafana) to track Redis memory usage and ensure it doesn’t exceed its limits.

  • Tune Redis settings: If you’re facing regular Redis failures, consider optimizing your Redis configuration. Increase the maxmemory-policy value in your Redis config file (/etc/redis.conf) to a higher number (e.g., 50) to allow more memory usage before evictions occur.

  • Regular maintenance: Schedule periodic Redis flushes or automatic reboots during off-peak hours to prevent memory buildup and ensure optimal performance.

Conclusion

By properly configuring Magento to use disk file cache as a fallback for Redis, you can minimize the impact of temporary Redis failures. This approach ensures that your store remains accessible to customers even when Redis becomes unavailable.

Remember to regularly monitor both Redis health and Magento performance to identify any potential bottlenecks proactively. If you need further assistance in optimizing your Magento setup or addressing specific caching issues, feel free to reach out to our expert team at Laravel Company.

Stay prepared for any eventuality, and your Magento store will continue to provide a seamless shopping experience for your customers.

Cache Admin Configuration Errors

Our network