Back up a bit: Why are your applications flushing a cache they share with other applications in the first place?
/Henrik On Wed, Dec 9, 2009 at 03:22, IvoLucien <[email protected]> wrote: > My guess is there is no standard way of flagging that a server is live > and that apps should not flush the cache, since apps just shouldn't do > that sort of thing without supervision. I'd love to be wrong. ^_^ > > With multiple versions and separate apps running on a server at once, > I need each app to check before flushing the cache. I want to emulate > a file write lock, where there are periods of time that the app is > actively dependent on the cache, and other times where it's kosher to > flush the whole enchilada. > > Would folks use a named semaphore to coordinate that, a mechanism > within memcached that I haven't found, or something else entirely? > > I want to prevent things like app A writing the first half of a set of > interdependent keys, app B flushing everything, then app A writing the > second half, potentially confounding itself later... Thanks much. >
