The locking should be handled directly by lucene, not in the NHS code. Note that if the indexing is done on a remote directory, the remote driver may fail to handle file locking appropriately. In those circumstances, it is recommended to have a single master, which all the nodes are queuing their updates for, which can update the index, that also tend to be much faster overall.
On Mon, Nov 24, 2008 at 5:54 PM, Vito <[EMAIL PROTECTED]> wrote: > > I've integrated NHibernate.Search into our company platform DAL and > it's works very fine. Compliments! Unfortunately, since two months > ago, our backend servers, where the DAL with NHibernate runs, are in a > NLB environment so different servers can update the Lucene file base > indexes at the same time. There is no a master backend and slave ones > because the NLB can return any backend server when a WCF call is made, > so all the backend nodes can contemporary update indexes to serve > different requests. > I've encountered a problem in the NHibernate.Search.Impl.Workspace > file because it is not able to correct manage the lock: (Monitor.Enter > & Monitor.Exit) and when it try to close the writer in the Cleanup > proc of the same class because sometimes the index files are already > locked by another backend. > Is there a new version that is able to run on distributed environments > or can I do anything to solve the problem? Thank u very much. > > --Vito > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "NHibernate Contrib - Development Group" 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.ar/group/nhcdevs?hl=en -~----------~----~----~----~------~----~------~--~---
