do a warm up heeh or use a memcached daemon with persistent storage (membase, memcachedb, or another memcache fork)
2011/7/8 Matthew John <[email protected]>: > Hi all, > > I am pretty new with memcached + membase. I tried using a combination > of both to serve my app's storage. Previously I used to work with > memcached + mysql. In that scenario, I used to frequently commit my > cache data to the database inorder to avoid data loss in the cache and > mysql is designed for that (immediate write). > > In this context, I have two queries: > > 1) But now, with membase advocating Lazy writes, how would I save the > data in my memcached in case of a server failure? Is there some way of > committing the memcached data into membase at some regular intervals? > > 2) Every time I recover from a failure, I would want to fill up my > memcached with data. In case of mysql, I could comfortably do a > "select * from *" inorder to fill up the memcached with the required > data. How would I do such a "warm up" in case of memcached + membase > combo? > > Please help me with these queries! :) :) > > Thanks, > Matthew > -- Roberto Spadim Spadim Technology / SPAEmpresarial
