invalidation by namespace Re: Listing all keys on a server: why?
pault12345 at yahoo.com
Fri Jul 28 20:25:50 UTC 2006
--- Serhat Sakarya <serhat at sakarya.nl> wrote:
> The only solution that springs readily to mind is to
> treat the revision
> > counter like any other cached value and store it
> in persistent storage as
> > well as in memcache.
> You could of course use mysql as persistent fallback
> storage for the keys,
> but that might be a bit too ironic.
Why is it ironic?
I think it is very consistent with the rest of the
1. The only way to have critical data survive hardware
failure of memecached node is to store those data in
persistent storage (which is usually mysql)
2. Salts are modified only when the namespace is
getting dropped ( == rarely )
Storing salts in presistent storage protects from the
hardware failure at no performance cost.
PS. Propagating the 'persistant storage' entity all
the way up to the caching client might make sense -
but that is another story.
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
More information about the memcached