Eric, No, I'm using the "memcached" gem which has a binding for libmemcached (and is much faster than the memcache-client gem).
The memcached gem has a compatibility wrapper (Memcached::Rails) which is made to be backwards compatible with memcache-client. Clifton On Thu, Mar 10, 2011 at 3:23 PM, Eric Wong <[email protected]> wrote: > Troex Nevelin <[email protected]> wrote: >> What is a right code for resetting memcache connection in after_fork for >> Rails 2.3 with "preload_app true" on REE? >> >> The only configurations about memcache in my app are: >> >> config/initializers/session_store.rb: >> ActionController::Base.session_store = :mem_cache_store >> >> config/environment.rb: >> config.cache_store = :mem_cache_store > > So that uses the memcache-client gem? I seem to remember that (and > dalli) only connects when it's needed, but I suppose some apps use > memcached at load time. > > The following should work, not the most elegant: > > before_fork do |server,worker| > ObjectSpace.each_object(MemCache) { |mc| mc.reset } > end > > An after_fork would probably send unnecessary messages to the memcached > servers. > >> I tried: >> Rails.cache.reset >> >> But it fails to start, looks like this code is for Rails3 only > > Hopefully somebody else knows a more elegant way to handle this. > > -- > Eric Wong > _______________________________________________ > Unicorn mailing list - [email protected] > http://rubyforge.org/mailman/listinfo/mongrel-unicorn > Do not quote signatures (like this one) or top post when replying > _______________________________________________ Unicorn mailing list - [email protected] http://rubyforge.org/mailman/listinfo/mongrel-unicorn Do not quote signatures (like this one) or top post when replying
