It sounds like you want one server to do the writing and one to do the reading (searching)? If so, why not do something like:
1. Have you writing server constantly updating the index 2. At some point, pause the writing process, then copy the directory over to your searching machine. 3. Point the searcher at the copied dir when the copy is done 4. Remove the old dir, and go back to 1 There are many tools to copy directories from one place to another (or to keep two filesystems in sync in general). I don't think this will be a lucene-specific issue. Thanks, -Ben --- On Wed, 11/17/10, Bing Li <[email protected]> wrote: > From: Bing Li <[email protected]> > Subject: How to Transmit and Append Indexes > To: [email protected] > Date: Wednesday, November 17, 2010, 1:58 AM > Hi, all, > > I am working on a distributed searching system. Now I have > one server only. > It has to crawl pages from the Web, generate indexes > locally and respond > users' queries. I think this is too busy for it to work > smoothly. > > I plan to use two servers at at least. The jobs to crawl > pages and generate > indexes are done by one of them. After that, the new > available indexes > should be transmitted to anther one which is responsible > for responding > users' queries. From users' point of view, this system must > be fast. > However, I don't know how I can get the additional indexes > which I can > transmit. After transmission, how to append them to the old > indexes? Does > the appending block searching? > > Thanks so much for your help! > > Bing Li >
