If you are using the distributed search server, there is not the
capability to add/remove servers to the search-servers.txt file and
these changes will get picked up in a few seconds. So the general
process would be:
1) do the reindexing in a different directory
2) startup a distributed search server pointing to the new directory
3) change the search-servers.txt file, remove old server and add new one
4) save search-servers.txt
5) shutdown old distributed search server.
The searcher.dir variable would remain constant and if you are running
the two search servers (new and old) on a single machine then simply use
different ports.
Dennis
[EMAIL PROTECTED] wrote:
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
