Re: [CLucene-dev] Multi-process access

[Kostka B. <ko...@to...>]

Hi,

You can share one index between any number of processes, which have index opened for reading.
You can also have one process which writes to the index at the same time.
If you add/delete some documents, you have to create new IndexReader in running searching processes to see the changes
You can use isCurrent method to check if index was changed.

Hope this help

Borek

From: Max . [mailto:ya...@li...]
Sent: Wednesday, April 23, 2014 10:55 PM
To: clu...@li...
Subject: [CLucene-dev] Multi-process access

Hi,

I am setting up a search engine based on CLucene which saved my life so thank you guys :) !
The idea is to have multiple servers do the indexing and other servers handle searching, I use a conventional round robin broker for that.
Each one of my client will have its own index, say bob connects to our web interface and searches for "foo" it will look it up in bob.idx so I will actually have lots of indexes.

I see two approach to this :
1) Have one index file on a NAS and everyone taps into that but I don't know how safe this is in terms of resource conflicts ?
2) Have indexers work on their own write-only index and replicate the index on search servers which will have read-only indexes and be put to sleep while the index is being replicated.

Can I have your opinions on approaching this problem ?

Thanks,
Max