Hi Richard,
it seems like lucene index replication could help you here: you could
create the index on the backend server and replicate it to the frontend
servers.
http://shaierera.blogspot.com/2013/05/the-replicator.html
<http://shaierera.blogspot.com/2013/05/the-replicator.html>
http://blog.mikemccandless.com/2017/09/lucenes-near-real-time-segment-index.html
<http://blog.mikemccandless.com/2017/09/lucenes-near-real-time-segment-index.html>
This way, the frontend servers can issue queries against their copy of
the index, and the backend server can perform updates that are then
replicated to the frontend server indexes.
Best regards
Christoph
On 01.09.2020 08:28, Richard So 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
