I recently received the following ticket info regarding some caching issues on our magento installation, and have run into some stumbling blocks in diagnosing (thus obviously fixing, as well) the underlying issue:

saving changes to any static content in the admin is no longer invalidating that page in the cache. E.g., editing a few words on the 'About Us' page and saving doesn't change anything on the front end, we'd then need to refresh the entire FPC to see our tiny tweak


The way it used to work (a few months back), is that upon saving a change, that page and only that page would update on the front end (taking a little longer to load because the cache for that page was invalidated).

At some point (not sure when), we began needing to flush the entire cache and redis cache for the change to appear, which meant the entire site's cache was cleared and everything loaded slowly (and the db takes a huge womping for a bit).

After a bit of that, we realized we didn't even need to flush the redis cache, as it seemed to make no difference, so we've just been flushing the magento cache after any changes ever since.


essentially upon updating the FPC module a while back, redis seems to have been cut out of the process of flushing the cache, so potentially it's been disconnected and may be the culprit.

In attempting to diagnose this problem, I've verified that everything on an applicable magento devdoc seems to be set up correctly between FPC and redis, as far as I can tell. IE app/etc/local.xml has the correct options for an installation not using Zend_Cache.

If anybody has any other ideas, or pointers on documentation that may help further with this issue, I would be very grateful. I seem to be having a bit of an issue locating decent magento documentation, on some issues, on this project. Thanks in advance!

Addendum: contents of local.xml follow

            <date><![CDATA[Tue, 12 Aug 2014 09:19:47 +0000]]></date>
                    <initStatements><![CDATA[SET NAMES utf8]]></initStatements>


          <server></server> <!-- or absolute path to unix socket -->
          <compression_lib>gzip</compression_lib> <!-- Supports gzip, lzf and snappy -->




1 Answer 1


It sounds like cache invalidation isn't happening. There are some additional notes to consider from Colin about the module Cm_Redis used in default installations as well that offer more insight. Particularly the garbage collection nightly. You may also look over the issues of the module to see if any others have reported similar issues.

Also, running multiple Redis instances for sessions/blocks/FPC may also help the pruning processes.

AOE_TemplateHints module is good for identifying a state of blocks cache that may help you debug the issue.

  • 1
    Thank you for the information that you've given so far; it's been very valuable. I was wondering if you might suggest where these notes from Colin about Cm_Redis might be found. I will also continue looking through the other references that you've given. We're already using multiple Redis instances (three I believe). Thank you very much for your time & help on this matter, @B00MER. May 31, 2015 at 17:09
  • 1
    I went ahead and edited the original post to included the contents of $INSTALLATION/app/etc/local.xml as per your request. I believe I've scrubbed it of all sensitive data. I'm seeing under the <fpc> section that the lifetime is set at 24 hours. I'm guessing that setting this to a shorter interval might bring about the behavior that we'd like to see; unfortunately I believe this would probably add an unacceptable amount of load avg to the server. Do you know if redis should automatically detect a static page modification (currently not happening)? Jun 15, 2015 at 22:26
  • 1
    Also, I wanted to thank you again, and also mention that we'll be looking into Munin and/or other interfaces to Redis to gain a little more insight on the behavior. Still very grateful for any insight that you might be able to impart on the matter, of course. :) Jun 15, 2015 at 22:27
  • 1
    I noticed you are using the same redis instance for each cache, it would be best to create a separate redis server instance for session, block and fpc. Also, you don't need to compress the FPC as its already compressed. This doc from Magento ECG may be helpful: info2.magento.com/rs/magentoenterprise/images/…
    – B00MER
    Jun 16, 2015 at 17:32
  • 1
    Yet another small update to this issue (though probably very important): It looks like we're using the Lesti extension for FPC. Sorry for the previous ambiguity. Also, being as this was kind of a conglomeration of issues after the FPC<-->redis issue was solved, I opened a new thread with this issue trimmed down just to the important components. Jun 18, 2015 at 22:42

Not the answer you're looking for? Browse other questions tagged or ask your own question.