On Thu, Dec 07, 2006 at 08:01:34PM +0100, Andreas Korth wrote: > > On 07.12.2006, at 19:19, Raymond O'connor wrote: > > > I may be a special case since my index is never updated through my > > frontend app, but I was planning on keeping one "gold" index on a > > backend server and update this index through a script whenever > > there are > > updates to my documents (about once a week in my case). This server > > will update the index and then do basically a cp to the frontend > > webservers and copy over the old indexes on each of these machines. > > What do people think of this solution? The searchable drb solution > > looks interesting though and I may consider it if I run into issues > > doing it this way. > > If updates happen so rarely, this might be a feasible solution. At > least, it involves less moving parts than an indexing server would > and it's faster than querying a remote server. I'm not sure, however, > if Ferret would like it if the index files are overwritten during a > read operation. You could write a capistrano recipe which shuts down > your app, updates the index files and restarts it afterwards. > Depending on the size of your index, this involves downtimes of a few > seconds which is certainly tolerable.
I'd suggest to swap out the whole index directory at once (something like 'mv index index.old && mv index.new index') and then re-open the Searcher. at least on unix/linux that should work without downtime. Jens -- webit! Gesellschaft für neue Medien mbH www.webit.de Dipl.-Wirtschaftsingenieur Jens Krämer [EMAIL PROTECTED] Schnorrstraße 76 Tel +49 351 46766 0 D-01069 Dresden Fax +49 351 46766 66 _______________________________________________ Ferret-talk mailing list [email protected] http://rubyforge.org/mailman/listinfo/ferret-talk
