I don't know what are your requisites, but when the update rate goes
up, the best solution is to go with "offline" updates. With
nhibernate.search you can batch the updates, and it could help a bit
with the indexing speed, but not with the lock issues. If you can
manage that just one server make the changes it would be the easiest
way.

In my case, usually whe update the index with a separate process that
check the changes since the last run and then publish the changes to
the search machines. (like the master-slave configuration of
nhibernate search)

If you can be more explicit with the environment and requisites i can
suggest you another approachs


On 24 nov, 16:54, 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
-~----------~----~----~----~------~----~------~--~---

Reply via email to