I've always wondered about the first part, but for the
second part, you don't have to restart the app server.
You might have to create a page or script that gets rid
of the nutch bean. Something like:
application.removeAttribute("nutchBean");
NutchBean bean = NutchBean.get(application);
Then just call this page after loading the new index
to the search dir.
Howie
> Date: Wed, 27 Feb 2008 21:52:54 +0000
> From: [EMAIL PROTECTED]
> To: [email protected]
> Subject: How to update search.dir with least interruption of service?
>
> When running a real world search engine, we will
> have a script to do the
> fetching all the time and
> re-index periodicly. I am wondering how people
> manage
> their segments/indexes data: do you let your crawl
> script write
> directly to webapp's 'search.dir', or
> let the crawl script write into one
> place then copy
> it over to 'search.dir'?
>
> And seems I have to restart
> J2EE server or at least
> re-deploy the webapp to let search.jsp read the
>
> new data. What is the best practice to have the
> least interruption of service?
>
>
> Thank you very much.
>
> Yong
>
>
_________________________________________________________________
Connect and share in new ways with Windows Live.
http://www.windowslive.com/share.html?ocid=TXT_TAGHM_Wave2_sharelife_012008
