FWIW, I agree with Michael: this is not a simple problem and there's been a lot of effort in Elasticsearch and Solr to solve it in a robust way. If you can't use ES/solr, I believe there are some posts on the ES blog about how they write/delete/merge shards (Lucene indices).
On Tue, Sep 1, 2020 at 11:40 AM Michael Sokolov <msoko...@gmail.com> wrote: > So ... this is a fairly complex topic I can't really cover it in depth > here; how to architect a distributed search engine service. Most > people opt to use Solr or Elasticsearch since they solve that problem > for you. Those systems work best when the indexes are local to the > service that is accessing them, and build systems to distribute data > internally; distributing via NFS is generally not a *good idea* (tm), > although it may work most of the time. In your case, have you > considered building a search service that runs on the same box as your > indexer and responds to queries from the web server(s)? > > On Tue, Sep 1, 2020 at 11:13 AM Richard So > <brothersevenlongl...@hotmail.com> wrote: > > > > Hi there, > > > > I am beginner for using Lucene especially in the area of Indexing and > searching simultaneously. > > > > Our environment is that we have several webserver for the search > front-end that submit search request and also a backend server that do the > full text indexing; whereas the index files are stored in a NFS volume such > that both the indexing and searchs are pointing to this same NFS volume. > The indexing may happen whenever something new documents comes in or get > updated. > > > > Our project requires that both indexing and searching can be happened at > the same time (or the blocking should be as short as possible, e.g. under a > second) > > > > We have search through the Internet and found something like this > references: > > > http://blog.mikemccandless.com/2011/09/lucenes-searchermanager-simplifies.html > > > http://blog.mikemccandless.com/2011/11/near-real-time-readers-with-lucenes.html > > > > but seems those only apply to indexing and search in the same server > (correct me if I am wrong). > > > > Could somebody tell me how to implement such system, e.g. what Lucene > classes to be used and the caveat, or how to setup ,etc? > > > > Regards > > Richard > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org > For additional commands, e-mail: java-user-h...@lucene.apache.org > >
