On 19.08.2014 17:55, Eric Johnson wrote: > Thanks for the excellent answers to my question! One more comment and > question below. > > On Tue, Aug 19, 2014 at 12:05 AM, Branko Čibej <br...@wandisco.com > <mailto:br...@wandisco.com>> wrote: > > Just remember to always restart the server after switching from > the old to the new repository to remove stale caches. (Yes, we're > currently working on making that mostly unnecessary in 1.9.) > > > What are these caches? I've got memcached turned off for these (fsfs) > repositories. What, exactly, do I need to restart? All client access > is via HTTP. Restarting Apache for each of my repository updates would > be unfortunate, because I want to keep the number of times I bounce > the server to a low value, even if it does only take 3s to restart.
These are in-process caches, specific to each individual HTTPd worker process. They have to be purged because otherwise a worker that's serving the repository while you make the switch may return stale information to clients -- possibly breaking working copies in the process. It's enough to do a graceful restart (apachectl graceful) when you switch the repository; this will restart the worker processes without actually making your server inaccessible. -- Brane -- Branko Čibej | Director of Subversion WANdisco | Realising the impossibilities of Big Data e. br...@wandisco.com
