Closed (works as designed)
Project:
Redis
Version:
7.x-2.0-beta1
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
15 Nov 2012 at 18:45 UTC
Updated:
16 Jan 2013 at 12:16 UTC
Saving or updating a node in Drupal triggers cache_clear_all(NULL, 'cache_page'), which in turn triggers the Redis clear() method and clears page caches. However, deleting a node does not trigger cache_clear_all. It uses an EntityController resetCache() method instead, which clears a static cache but doesn't actually clear the cache in the database. This means that Redis will return some stale content to users in situations where nodes have been deleted.
This issue bears some similarity to a previous issue that was reported and fixed for Redis previously:
Comments
Comment #1
sheldon rampton commentedI think this may be more of a Drupal core bug than a Redis bug, so I've filed a separate bug ticket against Drupal core:
http://drupal.org/node/1841900
Comment #2
pounardThanks, closing it. If you find out this is a Redis bug, please re open.