Listing all keys on a server: why?

Nathanial Thelen nate at
Thu Jul 27 17:50:42 UTC 2006

We had a use for memcached that made it not a caching solution, but
something else.  We were excited about the distributed, scalability of sets
and gets, and our data did not need to be persisted, but we did need to be
able to get the list of keys every couple seconds.

We ended up not using memcached and went with a more custom solution.


On 7/27/06 9:50 AM, "Jamie McCarthy" <jamie at> wrote:

> Hi everyone,
> Every once in a while I hear people musing that it'd be useful to get a
> list of all keys currently available in a memcached server.  If you're
> one of those people, please email me off-list, I'd like to kick ideas
> around with you.
> My current thinking is that, since:
> * one or more memcached servers may be down when you get your list
>   and come back up immediately afterwards
> * whatever you want the list for, it's not atomic with your next
>   memcached operation anyway
> ...the list you would get would be obsolete as soon as you got it.  So
> my guess would be that, if you think you need that list, you may be
> wanting to do something with memcached that you can't really do.  But my
> guesses are frequently wrong and if there's something I'm forgetting
> please email me and let me know.  Thanks.

Nathanial Thelen
LA: 323-938-4401 x203

AOL: natethelen
MSN: nate at

More information about the memcached mailing list