Thank you Brian. I appreciate your input! I'll go back to the Drupal docs and/or forums and poke around there some more.
Best, Stephen On Dec 7, 1:56 pm, Brian Moon <[email protected]> wrote: > On 12/7/10 3:17 PM, layman wrote: > > > > > > > > > > > Hello all, > > > I'm fairly new to memcached, and the documentation I've been reading > > on its use for Drupal, along with searching for answers in this group > > gives me enough to know that it is not normal for sessions to spin on > > the browser until they timeout when memcached is stopped. > > > The architecture is a cluster of two instances. Initially views would > > no longer work as soon as one of the instances was brought down. I > > found that we were not using unique key prefixes and corrected that. > > Now, whenever one memcached instances is stopped, things still work > > fine. > > > However, once I bring both memcached instances down, it doesn't treat > > hits as a cache miss. It doesn't appear to even go to the database > > for data, but just times out after the four minute period we've set > > for idleTimeout in PHP. > > > I presume this means that I am doing something fundamentally wrong > > here. I am not using any kind of custom setting in memcached other > > than just specifying a memory limit and the user to run it as. > > > Do you think this means that I should look at the Drupal application > > itself for clues on why it behaves in this way, or am I missing > > something on the memcache front? > > > Thanks for any help. > > Yes, it sounds like the Drupal implementation for memcached is not very > well done. I can tell you that using either of the memcached libraries > for PHP directly would not exhibit this behavior. > > -- > > Brian. > --------http://brian.moonspot.net/
