Hi all,

I'm about to dive into NH Search, but I am concerned about multiple
processes accessing a shared index.  I have several services and a web farm
all using the same NH entities and pointing to the same db.  Ideally I would
like all of the processes to be able to update a central Lucene index on a
network share since all of the processes will need search capabilities.  I
will be indexing approximately 2 million entities.  A small subset (1000?)
of those entities are updated very frequently (every minute or so).

Does anyone else have a similar setup, or an alternative solution?  Is there
going to be a concurrency issue setting up a shared index for all of these
processes?  How are others using NH Search over multiple processes?  I have
googled for info on the topic, but the results are somewhat sparse.  I have
read some old posts about IndexWriters timing out because other processes
have locks on the index; is that a concern?

Thanks!
-tyler burd

-- 
You received this message because you are subscribed to the Google Groups 
"nhusers" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/nhusers?hl=en.

Reply via email to