On Jun 19, 2008, at 1:20 PM, John Thompson wrote:
You can set up an account in Tomcat Manager if you don't have one
already.
The Manager lets you go in and independently start/stop/reload any
of the
different webapps you have running. This is exactly how I get new
Nutch
crawls/indexes to be active on our production server.
Won't restarting the webapp cause Tomcat to serve up error pages to
users
who are trying to connect to the webapp at that moment?
We set up our own servlet which uses a NutchBean in a Singleton
pattern. It runs an update thread which periodically checks a known
file which contains a directory name. When loading a new search db,
we copy the directory where we want it (we use a directory with a
date in the name) and edit the file to point to the new dir. A
client never has problems related to unavailability because they
either get the old NutchBean, referencing the old dir, or the new
NutchBean, referencing the new dir. We keep the old ones around for
a period of time (default 5 minutes) in case anyone has a search page
open and wants previous/next page of results.
We haven't run into any problems with this setup. If anyone wants
more information, let me know.
--
Eric J. Christeson
<[EMAIL PROTECTED]>
Information Technology Services (701) 231-8693 (Voice)
Room 242C, IACC Building
North Dakota State University, Fargo, ND 58105-5164
Organizations which design systems are constrained to produce designs
which
are copies of the communication structures of these organizations. (For
example, if you have four groups working on a compiler, you'll get a
4-pass compiler) - Conway's Law
